batch_edit

Apply manifest-driven multi-file edits with dry-run and rollback.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wjlmrzd/OpenClaw-Wren --skill batch-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch_edit
Source: https://github.com/wjlmrzd/OpenClaw-Wren/tree/main/skills/batch-edit
Command: npx skills add https://github.com/wjlmrzd/OpenClaw-Wren --skill batch-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures multi-file changes are applied atomically and consistently so that related edits (like API version bumps, import adjustments, or configuration updates) never leave the codebase in a partially-updated or broken state.

Core Features & Use Cases

  • Manifest-driven edits: define edit/create/delete steps in a structured manifest for deterministic execution.
  • Safety-first workflow: perform a dry-run to confirm exact matches, execute only if all checks pass, run verification commands, and automatically roll back on failure.
  • Practical use cases include API version migrations, coordinated refactors across modules, bulk renames, and creating/deleting related files as a single operation.
  • Built-in constraints and limits include text-only edits (no binaries), per-file size/line limits, and workspace path restrictions to prevent accidental external changes.

Quick Start

Apply a batch-edit manifest that replaces API version "v1" with "v2" across the workspace, run the dry-run to confirm exact matches, execute the changes atomically, and verify that no "v1" occurrences remain.

Frequently Asked Questions about batch_edit

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

FAQPage Schema
How do I atomically update related code and configuration across multiple files?

Atomic multi-file edits require a manifest-driven workflow where you define edit, create, and delete entries to consistently update related code and configuration without leaving the workspace partially updated.

What is the safest way to execute a coordinated API version migration across a workspace?

Executing a coordinated API version migration safely involves an initial dry-run to confirm exact old-text matches, applying changes only on full match, and running verification commands to ensure no broken states remain.

How do I roll back a bulk code refactor if post-change verification fails?

Automatic rollback on verification failure reverts the bulk code refactor by restoring the workspace to its pre-edit state, ensuring that partial updates or failed configurations are undone immediately.

Can I use manifest-driven batch edits to create and delete related project files simultaneously?

Manifest-driven batch edits support coordinated file creation and deletion alongside text edits, allowing you to manage related project files simultaneously during development and release workflows.

What are the limitations of applying atomic multi-file edits within a workspace?

Limitations of atomic multi-file edits include text-only modifications with no binary support, per-file size and line limits, and workspace path restrictions to prevent accidental external changes outside the project.

Why does my dry-run fail before executing a batch edit manifest?

A dry-run fails before executing a batch edit manifest when the exact old-text strings defined in the manifest do not match the current file contents, preventing execution to avoid inconsistent updates.