patch-edit
Apply one rewrite-plan step at a time as small reviewable file edits, never rewriting whole files when a localised change suffices.
Profile →npx skills add nexu-io/open-design --skill patch-edit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Patch edit 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". ## Inputs - `plan/steps.json` from `rewrite-plan`. - The current value of `iterations` (the daemon's per-stage counter). - `code/index.json` for the file's known imports + neighbours. ## Output The atom mutates files inside the project cwd via the `file-edit` tool. After every iteration, it writes a per-step receipt: ```text project-cwd/ └── plan/ ├── steps.json (status updated: 'pending' → 'completed' | 'skipped') └── receipts/ └── step-<id>.json # { files: ['...'], diffSummary, rationale, completedAt } ``` ## Convergence The atom completes when every step in `plan/steps.json` is in a terminal state (`completed` / `skipped`) OR `iterations >= OD_MAX_DEVLOOP_ITERATIONS`. Use: ```jsonc { "id": "patch-edit-loop", "atoms": ["patch-edit"], "repeat": true, "until": "plan.steps.terminal === plan.steps.total || iterations >= 8" } ``` ## Anti-patterns the prompt fragment forbids - Rewriting an entire file when the rewrite-plan step is loc
- Inputs
- Output
- Convergence
- Anti-patterns the prompt fragment forbids
- Status
What does the patch-edit skill do?
Apply one rewrite-plan step at a time as small reviewable file edits, never rewriting whole files when a localised change suffices.
How do I install it?
Run `npx skills add nexu-io/open-design --skill patch-edit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.