patch-edit

Apply localized file edits based on rewrite-plan steps to ensure reviewable code changes.

93.2k|10.8k|Updated Apr 28, 2026

Search Tags:#diff #Refactoring #Automation #devloop #code-migration #Patch

One-click install

npx skills add https://github.com/nexu-io/open-design --skill patch-edit

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: patch-edit
Source: https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/patch-edit
Command: npx skills add https://github.com/nexu-io/open-design --skill patch-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the difficulty of auditing large-scale code changes by enforcing a granular, step-by-step editing process that prevents opaque, whole-file rewrites.

Core Features & Use Cases

Atomic Edits: Applies changes as small, reviewable diffs rather than replacing entire files.
Receipt Generation: Records rationale and status for every individual step in the migration plan.
Use Case: When migrating a large codebase to a new framework, use this Skill to apply changes one function at a time, allowing for easier verification and rollback of specific steps.

Quick Start

Execute the patch-edit atom to process the pending steps defined in the project rewrite-plan.

Frequently Asked Questions about patch-edit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I apply code changes in small steps?▼

Use the patch-edit atom to process your rewrite-plan, which forces the agent to apply changes as localized, reviewable edits rather than rewriting entire files.

What happens if a rewrite step fails?▼

The atom records the failure in the step receipt and updates the status in plan/steps.json, allowing the daemon to track progress and handle retries or skips.

Can I use this for high-risk file modifications?▼

High-risk modifications require explicit user confirmation before the atom touches shell-tier files, ensuring that sensitive changes are not applied automatically.

How does the atom know when to stop?▼

The atom completes when all steps in the rewrite-plan reach a terminal state or when the iteration limit defined by OD_MAX_DEVLOOP_ITERATIONS is reached.