Focused Fix — Deep-Dive Feature Repair — Development

Focused Fix is a systematic, five-phase protocol for repairing an entire feature or module end-to-end. It guides the user through scoping the feature, tracing all dependencies, diagnosing every issue, fixing them in a strict order, and verifying the result with tests and consumer checks.

engineering claude-code

📂 View skill on GitHub ↗ 🚀 How to use

✨ What it does

Enforces a strict 5-phase protocol: SCOPE, TRACE, DIAGNOSE, FIX, VERIFY.
Maps the feature boundary and all inbound/outbound dependencies.
Runs comprehensive checks on code quality, runtime, tests, logs, and configuration.
Labels issues by risk (HIGH/MED/LOW) and requires root-cause confirmation.
Fixes issues in a specific order: dependencies, types, logic, tests, integration.
Includes escalation rule for cascading failures and red flags to prevent skipping phases.

🎯 When to use it

When the user asks to make a specific feature or module work end-to-end, such as 'make X work' or 'fix the Y feature'.
When a feature or module is reported as broken and requires systematic repair across multiple files and dependencies.
When the user says 'the Z module is broken' or 'focus on [area]' indicating a need for deep-dive repair.
When quick single-bug fixes are insufficient and the entire feature needs tracing, diagnosis, and coordinated fixes.

🚀 How to use

Trigger the skill by asking to fix or make a feature/module work end-to-end, e.g., 'make the login feature work' or 'the checkout module is broken'. The skill expects the user to specify the feature/folder if not clear. It will then guide through the five phases, producing manifests, reports, and a completion summary. Example prompts:

Make the authentication feature work properly.
The payment module is broken; fix it end-to-end.

📄 Output: The skill produces a completion report summarizing files changed, fixes applied, test results, and consumer verification.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering/skills/focused-fix .claude/skills/focused-fix

Skill source: engineering/skills/focused-fix/SKILL.md

⚠️ Good to know

This skill is not for quick single-bug fixes; it requires completing all phases before proposing fixes and may need user input to define the feature scope.

❓ FAQ

What is the Iron Law of Focused Fix?

The Iron Law states: NO FIXES WITHOUT COMPLETING SCOPE → TRACE → DIAGNOSE FIRST. You cannot propose fixes until Phase 3 is finished.

When should I use systematic-debugging instead?

Use systematic-debugging for single-bug fixes, not for entire feature repair. Focused Fix is for when an entire feature or module needs systematic repair.

What triggers the escalation rule?

If 3+ fixes in Phase 4 create new issues, stop and discuss restructuring with the user, as it indicates an architectural problem.

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.