ce1d7925cc
- Normalize SKILL.md frontmatter to repo standard (remove non-standard license, metadata.* fields; inline description) - Generate docs page (docs/skills/engineering/focused-fix.md) - Add to mkdocs.yml nav (skills + commands) - Create /focused-fix slash command (commands/ + .claude/commands/) - Add to cs-senior-engineer agent (skill integration + new workflow #4) - Update marketplace.json and plugin.json descriptions (30 → 31 skills) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
18 lines
962 B
Markdown
18 lines
962 B
Markdown
---
|
|
description: Deep-dive feature repair — systematically fix an entire feature/module. Usage: /focused-fix <feature-path>
|
|
---
|
|
|
|
Systematically repair the feature/module at `$ARGUMENTS` using the focused-fix 5-phase protocol.
|
|
|
|
If `$ARGUMENTS` is empty, ask which feature/module to fix.
|
|
|
|
Read `engineering/focused-fix/SKILL.md` and execute ALL 5 phases IN ORDER:
|
|
|
|
1. **SCOPE** — Map the feature boundary (all files, entry points, internal files)
|
|
2. **TRACE** — Map inbound + outbound dependencies across the entire codebase
|
|
3. **DIAGNOSE** — Check code, runtime, tests, logs, config. Assign risk labels (HIGH/MED/LOW). Confirm root causes with evidence.
|
|
4. **FIX** — Repair in order: deps → types → logic → tests → integration. One fix at a time, test after each. 3-strike escalation if fixes cascade.
|
|
5. **VERIFY** — Run all feature tests + consumer tests. Summarize changes.
|
|
|
|
**Iron Law:** No fixes before completing Phase 3. No exceptions.
|