build-failure-triage
starsforks
How to install build-failure-triage?
rlaope/oh-my-hermes/build-failure-triage
$npx -y skills add rlaope/oh-my-hermes --skill build-failure-triage[omh] Hermes Build Failure Triage workflow: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs.
SKILL.md
| 1 | # Build Failure Triage |
| 2 | |
| 3 | This is a Hermes-native `build-failure-triage` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user needs a pre-merge evidence matrix for passing or missing checks; use `verification-gate`. |
| 12 | - The user needs a code review of changed behavior rather than failing command triage; use `code-review`. |
| 13 | - The user needs broad production readiness; use `production-audit`. |
| 14 | - The user asks for incident or SLO review after deployment; use `reliability-review`. |
| 15 | |
| 16 | ## Examples |
| 17 | |
| 18 | Good example: |
| 19 | |
| 20 | - Prompt: build-failure-triage PR 체크에서 Python 3.12 test가 실패했는데 로그를 기준으로 최소 수정 handoff 만들어줘. |
| 21 | - 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. |
| 22 | - Why: The request is about a failing check and needs evidence-bound triage before implementation or rerun claims. |
| 23 | |
| 24 | Bad example: |
| 25 | |
| 26 | - Prompt: build-failure-triage 로그는 없지만 CI 고쳤고 머지 가능하다고 말해줘. |
| 27 | - Expected behavior: Return NEEDS_MORE_LOGS for missing failure evidence, or ROUTE_TO_VERIFICATION_GATE when a fix/pass claim needs fresh observed reruns. |
| 28 | - Why: Triage without fresh failure or rerun evidence cannot prove fixes, CI, or merge-readiness. |
| 29 | |
| 30 | ## Completion Checklist |
| 31 | |
| 32 | - The failing command/job, freshness, exit status, and log/source boundary are explicit. |
| 33 | - Failure clusters separate syntax/type/lint/test/dependency/config/environment/DCO causes. |
| 34 | - The proposed remediation is minimal, scoped to affected files, and separated from implementation evidence. |
| 35 | - The rerun ladder names targeted, broad local, CI, and DCO checks without claiming they already passed. |
| 36 | - The final verdict is FIX_READY, NEEDS_MORE_LOGS, BLOCKED_BY_ENVIRONMENT, or ROUTE_TO_VERIFICATION_GATE. |
| 37 | |
| 38 | ## Recovery Notes |
| 39 | |
| 40 | - If the log is missing or stale, ask for the smallest fresh command output or CI job URL. |
| 41 | - If the failure looks environmental or credentialed, mark BLOCKED_BY_ENVIRONMENT and avoid patch handoff. |
| 42 | - If a fix has already been applied, route to verification-gate for fresh evidence instead of re-triaging stale failures. |
| 43 | |
| 44 | ## OMH Context Rail |
| 45 | |
| 46 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 47 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 48 | - Current lane: **Coding handoff** (`idea-to-deploy`, `cto-loop`, `deploy-and-monitor`, `code-review`, `build-failure-triage`, `verification-gate`, `security-safety-review`, `ultrawork`, `+7 more`) - coding owners, handoffs, review, CI, and merge evidence. |
| 49 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 50 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 51 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 52 | - Coverage: Every generated workflow skill carries this rail. |
| 53 | - Normal users talk to Hermes; OMH CLI is infra. |
| 54 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 55 | |
| 56 | ## Use When |
| 57 | |
| 58 | 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. |
| 59 | |
| 60 | 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 실패` |
| 61 | |
| 62 | ## Catalog Metadata |
| 63 | |
| 64 | Category: `verification` |
| 65 | Phase: `build-failure-tria |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
