repair-in-place
Skill2 starsChanged yesterdayMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- niksavis/handilyword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- niksavis/handily★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-mailSkill
- best-practices-auditSkill
- catalog-authoringSkill
- cli-toolsSkill
- conventional-commitsSkill
- councilSkill
- decompose-planSkill
- falsify-firstSkill
- find-skillsSkill
- harness-clientSkill
- harness-loopSkill
- hill-climbSkill
- interface-factsSkill
- no-commentsSkill
- nodeSkill
- plain-englishSkill
- pythonSkill
- release-processSkill
- repair-in-placeSkill
- retention-probeSkill
- root-causeSkill
- session-finishSkill
- skill-creatorSkill
- swarmSkill
- test-disciplineSkill
- tier-injectionSkill
- validate-as-consumerSkill
- work-trackerSkill
- worktree-isolationSkill
- agent-mailSkill
- best-practices-auditSkill
- catalog-authoringSkill
- cli-toolsSkill
- conventional-commitsSkill
- councilSkill
- decompose-planSkill
- falsify-firstSkill
- find-skillsSkill
- harness-clientSkill
- harness-loopSkill
- hill-climbSkill
- interface-factsSkill
- no-commentsSkill
- nodeSkill
- plain-englishSkill
- pythonSkill
- release-processSkill
- retention-probeSkill
- root-causeSkill
- session-finishSkill
- skill-creatorSkill
- swarmSkill
- test-disciplineSkill
- tier-injectionSkill
- validate-as-consumerSkill
- work-trackerSkill
- worktree-isolationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Continue the existing task: Do not repeat refinement or create a new plan for an implementation defect.
- Very specific: line 21
Read the findings in the brief.
- Distinctive: line 22
Run the failing check in the worktree and read its output.
- Distinctive: line 25
Write a regression test that fails.
- Distinctive: line 27
Run the check again and read the summary line.
- Distinctive: line 28
Commit and integrate in the existing worktree workflow.
- Distinctive: line 30
Do not pass a size gate by deleting comments or other text, and do not pass a test by loosening its assertion.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- 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.
- Check the gate's premise before you obey its remedy. The repair advice of a gate can be wrong.
Procedure
- Read the findings in the brief. When the cause is unclear or the failure recurs, run
root-causefirst. - Run the failing check in the worktree and read its output.
- 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.
- Write a regression test that fails.
- Fix the cause, then check every other call site of the same code.
- Run the check again and read the summary line.
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

