Breaking change recovery
Skill chf3198/megingjord-harness/skills/breaking-change-recovery
AI agent governance harness: baton workflow, fleet LLM routing (Ollama/Claude/OpenRouter), and CI gates for Copilot, Claude Code, and Codex.
npx -y skills add chf3198/megingjord-harness --skill breaking-change-recoveryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Execute the six-phase breaking-change recovery workflow. Invoked from workflow-resilience Tier-3 escalation or manually when a merged commit breaks the runtime, schema, or governance pipeline.
SKILL.md
2.0 KB, as published. Nobody here has run it
Breaking-Change Recovery Skill
Reference: instructions/breaking-change-recovery.instructions.md
When to invoke
- Any role detects a P0/P1 runtime or schema breakage after a merge.
- Consultant Tier-3 escalation hands off to this skill.
Quick-start
- Identify the breaking commit SHA and causal issue number.
- Post
INCIDENT_OPENon the causal issue with severity + blocked teams. - Revert with
git revert <sha> --no-edit— merge immediately. - File triage ticket:
fix: [regression description]withtype:bug. - Fix on branch
fix/<triage-ticket#>-<slug>; add regression test. - Post
SMOKE_EVIDENCEbefore re-merge. - Re-author casualties: close original (
resolution:superseded), refile.
Smoke evidence block template
## SMOKE_EVIDENCE
fix_pr: #N
breaking_sha: <sha>
- [x] runtime starts without error
- [x] regression test passes
- [ ] governance hook fires correctly (schema/hook fixes)
- [ ] affected team confirms unblocked (P0 only)
Signed-by: <alias>
Team&Model: <team>:<model>@<substrate>
Role: admin
Worked example
Chain: #1917 (cause) → #1951 (triage) → #1952 / c857ce8 (fix)
→ #1953 (casualty closed) → #1954 (casualty refiled).
See full narrative in instructions/breaking-change-recovery.instructions.md
Phase 6 "Worked Example" section.
Escalation path
If the fix cannot be completed within one session, the Manager must post a
BLOCKER_NOTE on the triage ticket and elevate severity to P0.