omh-build-failure-triage
[omh] Hermes Build Failure Triage workflow: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs. Use when the user says: build-failure-triage, build failure triage, build failure, build-failure, build fix, build failed, build failing, compile error.
rlaope · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add rlaope/oh-my-hermes --skill omh-build-failure-triage技能说明
name: "omh-build-failure-triage" description: "[omh] Hermes Build Failure Triage workflow: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs. Use when the user says: build-failure-triage, build failure triage, build failure, build-failure, build fix, build failed, build failing, compile error." metadata: hermes: tags: [workflow, oh-my-hermes, verification] category: verification phase: build-failure-triage role: reviewer quality_tier: build-failure-triage-gated
Build Failure Triage
This is a Hermes-native build-failure-triage workflow skill.
Why This Exists
build-failure-triage adapts ECC's build-fix and PR-test-analysis posture into an OMH-native workflow so failed checks become evidence-backed minimal handoffs instead of ad hoc debugging or false-green verification claims.
Do Not Use When
- The user needs a pre-merge evidence matrix for passing or missing checks; use
verification-gate. - The user needs a code review of changed behavior rather than failing command triage; use
code-review. - The user needs broad production readiness; use
production-audit. - The user asks for incident or SLO review after deployment; use
reliability-review.
Examples
Good example:
- Prompt: build-failure-triage PR 체크에서 Python 3.12 test가 실패했는데 로그를 기준으로 최소 수정 handoff 만들어줘.
- Expected behavior: Prepare failure_log_digest/v1, failure_cluster_matrix/v1, root-cause hypotheses, minimal_fix_handoff/v1, rerun_plan/v1, and a FIX_READY verdict without claiming CI is fixed.
- Why: The request is about a failing check and needs evidence-bound triage before implementation or rerun claims.
Bad example:
- Prompt: build-failure-triage 로그는 없지만 CI 고쳤고 머지 가능하다고 말해줘.
- Expected behavior: Return NEEDS_MORE_LOGS for missing failure evidence, or ROUTE_TO_VERIFICATION_GATE when a fix/pass claim needs fresh observed reruns.
- Why: Triage without fresh failure or rerun evidence cannot prove fixes, CI, or merge-readiness.
Completion Checklist
- The failing command/job, freshness, exit status, and log/source boundary are explicit.
- Failure clusters separate syntax/type/lint/test/dependency/config/environment/DCO causes.
- The proposed remediation is minimal, scoped to affected files, and separated from implementation evidence.
- The rerun ladder names targeted, broad local, CI, and DCO checks without claiming they already passed.
- The final verdict is FIX_READY, NEEDS_MORE_LOGS, BLOCKED_BY_ENVIRONMENT, or ROUTE_TO_VERIFICATION_GATE.
Recovery Notes
- If the log is missing or stale, ask for the smallest fresh command output or CI job URL.
- If the failure looks environmental or credentialed, mark BLOCKED_BY_ENVIRONMENT and avoid patch handoff.
- If a fix has already been applied, route to verification-gate for fresh evidence instead of re-triaging stale failures.
Workflow Lane
- Current lane: Coding handoff (
idea-to-deploy,llm-app-dev,cto-loop,deploy-and-monitor,code-review,build-failure-triage,verification-gate,security-safety-review,+13 more) - coding owners, handoffs, review, CI, and merge evidence. - If intent belongs to another lane, hand back to
oh-my-hermesor name the adjacent workflow. - Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when Hermes must inspect a failing build, typecheck, lint, test, CI, or DCO signal and prepare the smallest evidence-backed remediation handoff without redesigning the system.
Strong routing signals: `build-failure-triage`, `build failure triage`, `build failure`, `build-failure`, `build fix`, `build failed`, `build failing`, `compile error`, `compilation error`, `typecheck failed`, `typecheck failure`, `type check failed`, `tsc failed`, `lint failed`, `lint failure`, `test failed`, `test failure`, `tests failed`, `ci failed`, `ci failure`, `github actions failed`, `pr checks failed`, `pr check failure`, `dco failed`, `dco failure`, `pytest failed`, `pytest failure`, `cargo build failed`, `npm build failed`, `ビルド失敗`, `ビルドが失敗`, `コンパイルエラー`, `型チェック失敗`, `テストが落ちる`, `빌드 실패`, `배포 파이프라인`, `파이프라인 깨짐`, `파이프라인 실패`, `배포 실패`, `CI 실패`, `빌드 고쳐`, `컴파일 에러`, `타입체크 실패`, `테스트 실패`, `체크 실패`, `DCO 실패`, `构建失败`, `編譯錯誤`, `编译错误`, `类型检查失败`, `测试失败`
Catalog Metadata
Category: verification
Phase: build-failure-triage
Hermes role: reviewer
Quality tier: build-failure-triage-gated
Reasoning demand: standard
Quality bar:
- Group failures by root cause and dependency order, not by raw log order alone.
- Recommend the smallest safe fix path and name when no fix is justified without more logs.
- Prefer targeted reruns before broad expensive checks, then broaden only when the changed surface requires it.
- Preserve exact observed failure snippets or file references without treating them as current PASS evidence.
Handoff policy:
Keep failure collection, grouping, root-cause hypothesis, retry policy, and minimal-fix handoff in Hermes. Command reruns, code edits, dependency installs, CI reruns, and merge readiness require observed executor, wrapper, or user evidence.
Required inputs:
- failing command, CI job, PR check, or tool name
- fresh failure log, exit status, or observed check URL
- repo root, branch, PR, or changed files under investigation
- allowed remediation boundary: diagnose only, local fix handoff, or executor-owned patch
- dependency-install and network permission boundaries
- last known passing state when available
Expected outputs:
- build_failure_triage_plan/v1
- failure_log_digest/v1
- failure_cluster_matrix/v1
- root_cause_hypothesis_set/v1
- minimal_fix_handoff/v1 when remediation is requested
- rerun_plan/v1
- build_failure_triage_verdict/v1
Artifact expectations:
- build_failure_triage_plan/v1 with failing surface, freshness, affected files, allowed actions, and stop condition
- failure_log_digest/v1 preserves exact command/job, exit status, top frames, file