Installs into .claude/skills of the current project.
Are you the author of Repair In Place?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/niksavis-repair-in-place)
---
name: repair-in-place
description: Fixes a named defect in the lane's own worktree from its findings, with no new plan. Use at REPAIR after verify or validate failed.
---
<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. -->
# Repair in place
Repair is a mode of the implementer, not a new start.
It uses the same worktree, the same scope and the same artifact. Use the findings together with the whole task acceptance contract.
## Rules
- **Continue the existing task.** Do not repeat refinement or create a new plan for an implementation defect.
- **Identify actual scope changes.** Resolve missing facts from the repository; ask only when a plan defect changes the approved outcome or needs new authority.
- **Fix in the lane's worktree, never by re-dispatch.** A re-dispatch pays the scope-reading cost again with less budget.
- **Reproduce before you fix.** Run the failing check and read its actual output.
- **Check the gate's premise before you obey its remedy.** The repair advice of a gate can be wrong.
- **Fix the cause at every call site.** A defect that came through a shared helper reached the other callers too.
- **Never weaken the gate that failed.** See the confirmation list in the always-on rules.
## Procedure
1. Read the findings in the brief.
2. Run the failing check in the worktree and read its output.
3. Build any test fixture from the observed error, never from a suspected message.
A fixture built from a guess tests a failure that never occurs.
4. Write a regression test that fails.
5. Fix the cause, then check every other call site of the same code.
6. Run the check again and read the summary line.
7. Commit and integrate in the existing worktree workflow. Loop-managed tasks may use their landing transition; direct observer repairs use ordinary Git and disclose any authorized hook bypass.
Do not pass a size gate by deleting comments or other text, and do not pass a test by loosening its assertion.
Both make the gate green over the defect it exists to catch.
