Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/patch-edit
Apply one rewrite-plan step at a time as small reviewable file edits, never rewriting whole files when a localised change suffices.
Passed 13 of 19 test cases with the skill, and 5 of 19 without it.
and 8 more in the full report
10 fixed6 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which variable tracks the current iteration count for the daemon stage loop when checking against maximum allowed iterations?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies iterations as the per-stage counter variable. | Missed | Passed |
The instructions your model reads when the skill loads.
Spec §20.3 / §21.3.2: code-migration / tune-collab cannot ship a trustworthy diff when the agent rewrites whole files in one pass — the reviewer can't audit the change. This atom enforces "one step per turn, smallest possible localised edit".
plan/steps.json from rewrite-plan.iterations (the daemon's per-stage counter).code/index.json for the file's known imports + neighbours.The atom mutates files inside the project cwd via the file-edit tool.
After every iteration, it writes a per-step receipt:
project-cwd/
└── plan/
├── steps.json (status updated: 'pending' → 'completed' | 'skipped')
└── receipts/
└── step-<id>.json # { files: ['...'], diffSummary, rationale, completedAt }
The atom completes when every step in plan/steps.json is in a
terminal state (completed / skipped) OR iterations >= OD_MAX_DEVLOOP_ITERATIONS. Use:
{
"id": "patch-edit-loop",
"atoms": ["patch-edit"],
"repeat": true,
"until": "plan.steps.terminal === plan.steps.total || iterations >= 8"
}
test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.