apply-patch

Apply structured multi-file patches with Add, Update, Delete, and Move operations.

6|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Acosmi/CrabClaw --skill apply-patch-acosmi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply-patch
Source: https://github.com/Acosmi/CrabClaw/tree/main/docs/skills/tools/fs/apply-patch
Command: npx skills add https://github.com/Acosmi/CrabClaw --skill apply-patch-acosmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patch-based changes across many files are error-prone and hard to audit; this skill provides a structured patch workflow to apply coordinated edits reliably.

Core Features & Use Cases

  • Structured patch format with Begin Patch / End Patch blocks to perform Add/Update/Delete/Move across files.
  • Plan-confirmation workflow to ensure human-in-the-loop before applying destructive changes.
  • Supports batch refactors and multi-file updates with safe rollback within the workspace.

Quick Start

Provide a patch block using Begin Patch/End Patch to modify your codebase.

Frequently Asked Questions about apply-patch

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

FAQPage Schema
How do I apply coordinated multi-file patches across a codebase?

To apply coordinated multi-file patches, provide a structured patch block using Begin Patch and End Patch syntax. This defines Add, Update, Delete, and Move operations to execute synchronized updates across your project files reliably.

What is the structured patch format for batch-editing code?

The structured patch format for batch-editing code uses Begin Patch and End Patch blocks to declare file-level operations. It standardizes Add, Update, Delete, and Move actions to ensure multi-file changes are applied predictably and safely.

Can I review multi-file changes before they are applied to my workspace?

Yes, multi-file changes require a plan-confirmation workflow before execution. This human-in-the-loop step ensures you review and approve coordinated edits, preventing destructive updates within the workspace-scoped sandbox.

What is the best way to perform bulk code refactoring across multiple files?

The best way to perform bulk code refactoring is using a structured patch workflow with plan confirmation. This approach safely coordinates updates, additions, deletions, and file moves across large projects while maintaining auditability.

Does multi-file patch application support safe rollback within the workspace?

Yes, multi-file patch application supports safe rollback within the workspace. This allows you to revert coordinated edits and synchronized updates if batch refactoring operations produce unexpected results.

When do I need to use a structured patch format for code refactoring?

You need a structured patch format for code refactoring when applying synchronized updates across many files. It prevents errors during bulk changes by enforcing a standardized syntax and a plan-confirm workflow within a sandbox.