Guide · Agent skill
How to use the Patch Edit agent skill (patch-edit)
Updated · written with AI from the project's own documentation and checked against our catalogue data
Patch Edit is an agent skill that makes an AI agent carry out a multi-step code change, such as a migration, one step at a time, using the smallest localised edit it can. It is written for developers and reviewers who want each change to be small enough to audit. After this guide you will know what the skill does, how to install it, how to ask for it in plain language, and what it needs to run.
Patch Editnexu-io/open-design · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Download the patch-edit skill ZIP from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. Alternatively, upload the ZIP under Settings → Capabilities → Skills.
- 4Prepare the plan. Run the rewrite-plan step so plan/steps.json and code/index.json exist in the project.
- 5Ask for the step. Request the next pending step be applied as a small, localised edit.
- 6Review the receipt. Check plan/receipts/step-<id>.json for the files changed, the diff summary and the rationale.
What is an agent skill, and what does Patch Edit do?
An agent skill is a folder containing a SKILL.md file that gives an AI agent specific instructions for one kind of task. The agent loads the skill when a request matches its description.
Patch Edit applies one rewrite-plan step at a time as small, reviewable file edits. It avoids rewriting whole files when a localised change is enough. For each step it edits only the files that step lists, so a person can review each change on its own.
- Works through a plan one step per iteration instead of making one large pass.
- Edits only the files listed in a step's files[] field.
- Writes a receipt per step with the files changed, a diff summary, and the reason.
- Stops when every step is completed or skipped, or when the iteration limit is reached.
Install the Patch Edit skill
Download the ZIP for the patch-edit skill from this page. Then choose one of the two install routes below.
For a personal skill available in all your projects, unzip it into ~/.claude/skills/. For a skill that only applies to one project, unzip it into that project's .claude/skills/ folder.
In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills → upload the ZIP
How to trigger Patch Edit with a natural request
The agent decides to use a skill from its description. The patch-edit description refers to applying one rewrite-plan step at a time as small reviewable edits, so ask for that kind of work in plain terms.
Patch Edit is designed for a plan that already exists. Its inputs are plan/steps.json from the rewrite-plan step, the current iterations counter, and code/index.json. Without those, the skill has nothing to work from.
- "Apply the next pending step in plan/steps.json as a small edit and write its receipt."
- "Continue the migration one step at a time and keep each diff reviewable."
- "Do not rewrite whole files. Make the smallest localised change for each step."
Examples of what the skill does in a run
In a code migration, each pending step in plan/steps.json is handled in its own iteration. The agent edits the files listed in that step, then records a receipt at plan/receipts/step-<id>.json containing files, diffSummary, rationale and completedAt. The step's status changes from pending to completed or skipped.
The skill also enforces limits. It will not touch a file outside the step's files[] list, and it will not change a shell-tier file unless the step's risk is 'high' or the user has confirmed the change. A skipped step still needs a receipt and a rationale.
project-cwd/
└── plan/
├── steps.json
└── receipts/
└── step-<id>.jsonWhat Patch Edit needs and safety notes
Patch Edit is built for the Open Design daemon. The SKILL.md alone does not supply the plan file, the file-edit tool, or the runner, so it will not work as a standalone skill. You need the daemon with its plan/steps.json and rewrite-plan step, and file-edit tool access within the project working directory.
The skill runs scripts and uses no network, according to its listing. The daemon runner that implements it validates step ownership and risk, applies unified diffs with atomic writes, and records receipts and progress. Review each receipt, especially for shell-tier files.
- Requires: Open Design daemon, plan/steps.json, rewrite-plan output, file-edit access inside the project directory.
- Runs scripts: yes. Uses network: no.
- Convergence stops when all steps are terminal or the iteration limit is reached.
Tips for getting reliable diffs
Run rewrite-plan first and check that plan/steps.json lists the files for each step. Patch Edit can only work within those lists.
Review receipts as they are written. Each one gives you the files, the diff summary and the reason, which is the quickest way to catch a bad step early.
- Keep steps small so each diff stays easy to read.
- Use the convergence loop with an explicit limit, for example until all steps are terminal or iterations reach 8.
- Do not use Patch Edit for quick one-off fixes; the plan and receipt process adds overhead.
{
"id": "patch-edit-loop",
"atoms": ["patch-edit"],
"repeat": true,
"until": "plan.steps.terminal === plan.steps.total || iterations >= 8"
}What people use it for
- Running a planned code migration one step at a time with a reviewable diff for each step.
- Producing a receipt and rationale for each change so reviewers can audit the work.
- Working through a refactor plan produced by the Open Design pipeline's rewrite-plan step.
Frequently asked questions
How do I install the patch-edit agent skill?
Download the patch-edit ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one project. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
Does patch-edit work on its own?
No. The SKILL.md alone does not supply the plan file, the file-edit tool, or the runner, so it needs the Open Design daemon. It reads plan/steps.json and code/index.json, which come from the rewrite-plan step.
Is patch-edit free?
The source describes the item as licensed under Apache-2.0. It does not list a price, so check the licence text for terms.
What does patch-edit need to run?
It needs the Open Design daemon with its plan/steps.json and rewrite-plan step, file-edit tool access within the project working directory, and earlier output from the rewrite-plan atom.
Does patch-edit use the network?
According to the listing, it runs scripts but does not use the network. Shell-tier files are only changed for high-risk steps or with explicit user confirmation.
When should I not use patch-edit?
Skip it for quick one-off edits or small fixes, where the plan, step and receipt machinery adds overhead without benefit. It is also not suited to unreviewed bulk changes to shell-tier files.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Patch Edit suits developers and teams running a planned migration or refactor who want small, auditable diffs and a receipt for each step, especially inside the Open Design pipeline. It is a poor fit for quick fixes, for use outside the Open Design daemon, or for bulk changes to shell-tier files without review.
Download the skill