fix-dev

Diagnose and patch a single defect found during code review or verification.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/byron1st/personal-harness --skill fix-dev-byron1st
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-dev
Source: https://github.com/byron1st/personal-harness/tree/main/skills/fix-dev
Command: npx skills add https://github.com/byron1st/personal-harness --skill fix-dev-byron1st

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a review or verification gate catches a bug after implementation, you need a disciplined way to fix exactly that defect without scope creep, accidental commits, or clobbering uncommitted work in the tree. ## Core Features & Use Cases - Bounded defect repair: Fixes one defect per invocation against established intent, escalating to needs-confirmation when the root cause demands new design work instead. - Worktree protection: Snapshots git status before editing, never overwrites pre-existing changes, never commits, and verifies only expected files moved. - Regression coverage and reporting: Adds or reuses a failing test, verifies proportionally, and appends a structured Fix entry to the existing Implementation Report. - Use Case: A reviewer flags REVIEW-003 — a null check missing in a parser. Invoke the skill with the finding; it locates the root cause, applies the smallest correct patch, adds a regression test, and returns a concise summary without committing. ## Quick Start Ask the agent to fix the failing login redirect bug found in review finding REVIEW-003 without committing any changes.

Frequently Asked Questions about fix-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a bug found during code review without a new plan?▼

Invoke the fix-dev skill with the defect description, expected behavior, and any reproduction pointer. It locates the root cause, applies the smallest correct change, adds a regression test, and returns a summary without committing.

How to fix a defect without overwriting uncommitted changes?▼

The skill captures git status before editing, reads staged and unstaged diffs of dirty target files, and never resets or discards pre-existing changes. After the fix it compares against the snapshot to confirm only expected files moved.

When should a bug fix go to plan-dev instead of fix-dev?▼

Route to plan-dev when the fix requires new public contracts, new features, or a change in product direction. If fix-dev discovers this after reading the code, it returns needs-confirmation with a sketch of the proper plan and edits nothing.

Does fix-dev commit the fix automatically?▼

No. The skill never commits and leaves the working tree as-is for the user. It also stays on the current branch with no branching, switching, or merging.

What happens when the defect cannot be reproduced or located?▼

The skill returns blocked, naming precisely what information is missing, and does not edit on speculation. Blocked and needs-confirmation results are never retried automatically.

How many retry attempts does fix-dev allow on a failing fix?▼

It stops after three failed attempts on the same error and returns failed. The skill itself does not retry under a different model; only the surrounding dev-loop may restart the persona once.