[omh] Hermes Build Failure Triage workflow: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs.
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/18/2026
What it changes
Passed 19 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill86%
Checks it passed that the model alone missed
Output FIX_READY as the triage verdict.
Return NEEDS_MORE_LOGS as the triage verdict.
Return FIX_READY as the triage status verdict.
and 15 more in the full report
14 fixed5 passed either way3 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+110%
Agent turns
0%
Response time
+3%
Model gemini-3.6-flashMeasured 8/18/2026v219 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
We deployed v2.4.0 to production two hours ago and our latency SLO was breached due to high error rates in microservice B. Please review the post-deployment incident and help us investigate the runtime SLO violation.
What was checked, without and with the skill
Checked
Without skill
With skill
Direct the request to reliability-review for post-deployment incident investigation.
Missed
Passed
Refrain from generating a build failure triage fix handoff.
Passed
Passed
case-06 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md128 linessingle file
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.