isolate-the-specific-failure-mode-before-proposing-a-fix — skill
isolate-the-specific-failure-mode-before-proposing-a-fix is a Claude Code skill that identifies the cause of each test failure before fixes, keeping unrelated failures in separate patches.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill isolate-the-specific-failure-mode-before-proposing-a-fix -a claude-codeWhat isolate-the-specific-failure-mode-before-proposing-a-fix does
The skill enforces a disciplined debugging workflow. The agent must isolate the failure mode first and ensure that every proposed change addresses exactly one root cause.
It includes checklists for reviewers and test engineers. A reviewer verifies that each required debugging step is visible in the diff, while tests must cover the failure condition. For multi-agent workflows, it defines a delegation line pointing to the local SKILL.md path.
Bundling unrelated bug fixes into one patch is prohibited by design. Each failure mode requires its own targeted diagnosis.
What it helps with
- isolate exact failure causes before proposing code changes
- keep fixes scoped strictly to a single root cause
- verify in code review that changes tackle one issue
- add tests for specific failure scenarios
Example prompts for the agent
- Isolate the specific failure mode in this broken test before writing any fix.
- Diagnose each failing test separately and address only one root cause per patch.
How to install isolate-the-specific-failure-mode-before-proposing-a-fix
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill isolate-the-specific-failure-mode-before-proposing-a-fix -a claude-code2Manually: put the files in place
~/.claude/skills/isolate-the-specific-failure-mode-before-proposing-a-fix/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/isolate-the-specific-failure-mode-before-proposing-a-fix/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill isolate-the-specific-failure-mode-before-proposing-a-fix -a codex2Manually: put the files in place
.agents/skills/isolate-the-specific-failure-mode-before-proposing-a-fix/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill isolate-the-specific-failure-mode-before-proposing-a-fix -a cursor2Manually: put the files in place
.cursor/skills/isolate-the-specific-failure-mode-before-proposing-a-fix/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .opencode/skills/generated/isolate-the-specific-failure-mode-before-proposing-a-fix2Manually: put the files in place
.github/skills/isolate-the-specific-failure-mode-before-proposing-a-fix/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill isolate-the-specific-failure-mode-before-proposing-a-fix -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .opencode/skills/generated/isolate-the-specific-failure-mode-before-proposing-a-fixManually: put the files in place
.devin/skills/isolate-the-specific-failure-mode-before-proposing-a-fix/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill isolate-the-specific-failure-mode-before-proposing-a-fix -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about isolate-the-specific-failure-mode-before-proposing-a-fix
How to install isolate-the-specific-failure-mode-before-proposing-a-fix in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill isolate-the-specific-failure-mode-before-proposing-a-fix -a claude-code. The file will be placed in ~/.claude/skills/isolate-the-specific-failure-mode-before-proposing-a-fix/SKILL.md.
What does isolate-the-specific-failure-mode-before-proposing-a-fix do?
It directs AI agents to diagnose why an error occurred before drafting code. It prevents combining fixes for unrelated root causes into a single patch.
What checks does this skill mandate?
Reviewers must verify that each required action is visible in the diff. Test engineers must add or update tests for the trigger conditions.
Source text
SKILL.md · MIT
--- name: isolate-the-specific-failure-mode-before-proposing-a-fix description: isolate the specific failure mode before proposing a fix metadata: generated_from_knowledge: '["a704dc0a-e0a1-42c3-a43e-b0eff135f657"]' source_knowledge_ids: '["a704dc0a-e0a1-42c3-a43e-b0eff135f657"]' generated_at: "2026-07-06T14:02:41.486Z" confidence: "0.60" status: active version: "1" skill_origin: generated --- <!-- generated by opencode-swarm skill-generator. Do not edit by hand; edits will be preserved on regeneration only with controlled update mode. --> # isolate the specific failure mode before proposing a fix ## Trigger - (no explicit trigger metadata; cluster derived from category/tags) ## Required Procedure - isolate the specific failure mode before proposing a fix - verify each fix addresses exactly one root cause ## Forbidden Shortcuts - (none recorded) ## Delegation Template When delegating a task affected by this skill, include: ``` SKILLS: file:.opencode/skills/generated/isolate-the-specific-failure-mode-before-proposing-a-fix/SKILL.md ``` ## Reviewer Checks - Verify each required action above appears in the diff. ## Test Engineer Checks - Add or update tests covering the trigger condition and the forbidden shortcut. ## Source Knowledge IDs - a704dc0a-e0a1-42c3-a43e-b0eff135f657 — When a test fails, diagnose each failure mode separately and apply targeted fixes — do not combine unrelated root causes into a single patch.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm