aii-safe-edit

Edits related file sets as one batch with version bumps and a changed-versus-unchanged manifest.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/maestroventures/aiintegrator --skill aii-safe-edit-maestroventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aii-safe-edit
Source: https://github.com/maestroventures/aiintegrator/tree/main/plugins/aii-blueprint/skills/aii-safe-edit
Command: npx skills add https://github.com/maestroventures/aiintegrator --skill aii-safe-edit-maestroventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing one file in a set of linked files (preferences, project files, skill families, templates) often leaves sibling files stale, so the set contradicts itself. This Skill turns every such edit into a clean batch so no shared fact drifts out of sync. ## Core Features & Use Cases - Batch editing of file sets: Maps every file a change touches, applies the change everywhere it belongs in one pass, and enforces the rule that one fact lives in exactly one file. - Honest version discipline: Bumps version stamps only on files that actually changed, keeping versions a truthful signal of what moved. - Changed-vs-unchanged manifest: Ships a scannable manifest listing every file in the set and its status, then hands off to a verification pass that greps for leftover old values. - Use Case: You rename a project value stored in a preferences bundle shared by four files. The Skill updates all four in one batch, bumps versions only on the files that changed, and produces a manifest proving no stragglers remain. ## Quick Start Ask the assistant to use the safe edit skill to rename a value across my preferences file set and show me the changed-versus-unchanged manifest.

Frequently Asked Questions about aii-safe-edit

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

FAQPage Schema
How do I edit multiple related files without leaving them inconsistent?

Map every file the change touches first, then apply the change to all of them in one batch pass. Bump version stamps only on files that actually changed and produce a manifest listing each file as changed or unchanged.

How do I keep shared facts consistent across a documentation set?

Enforce the rule that one fact lives in exactly one file: designate an owning file and have other files link to it instead of copying the value. If the same fact appears in multiple files, treat it as a duplication bug and fix ownership before editing.

Should I bump version numbers on all files in a set after an edit?

No. Bump the version stamp only on files that actually changed; unchanged files keep their existing version. Blanket-bumping the whole set destroys the version's value as a truth signal about what moved.

How do I verify a batch file edit left no stale values behind?

After producing the changed-versus-unchanged manifest, grep the entire set for the old values and confirm zero matches remain. The manifest is a claim, not proof, so a separate verification pass must confirm it before reporting the batch complete.

When should I not use a batch editing workflow?

Skip the batch machinery for standalone files that share nothing with other files and for scratch or work files. The full batch process only applies when an edit touches a set of linked files sharing facts, versions, naming, or cross-references.