focused-fix
The focused-fix command executes a systematic five-phase protocol to repair an entire feature or module by mapping its scope, tracing dependencies, diagnosing root causes with risk assessment, applying fixes sequentially with testing, and verifying all related tests pass. Use this when addressing substantial bugs or malfunctions that span multiple files or layers within a codebase.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.claude/commands/focused-fix.md -o ~/.claude/commands/focused-fix.mdfocused-fix.md
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.
Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
Stage working tree changes and create a Conventional Commit (no push).
Stage, commit, and push the current branch following git governance rules.
Create a pull request from the current branch.
Run the full 8-phase plugin audit pipeline on a skill directory.
Run the local review gate before pushing.
Run the security scan gate before pushing.
Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.