| name | isolate-the-specific-failure-mode-before-proposing-a-fix |
| description | isolate the specific failure mode before proposing a fix |
| 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.6 |
| status | active |
| version | 1 |
| skill_origin | generated |
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
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.
