Surgical Edits
Use when editing existing code — making a fix, adding a feature, or changing behavior in a file that already has working code. Enforces minimal, scoped diffs so the agent changes only what the task requires and never refactors, reformats, or "improves" untouched code.
Install
$ agentstack add skill-buildmoonshot-skillpacks-surgical-edits ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-buildmoonshot-skillpacks-surgical-edits) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Surgical Edits
When modifying existing code, change only what the task requires. Every line in your diff must trace directly back to the request.
Rules
- Touch only what's required. Do not edit, reorder, or reformat code outside the scope of the task — even if you would normally write it differently.
- Match the surrounding style. Mirror the existing naming, indentation, quote style, and comment density of the file you're editing, not your personal defaults.
- No drive-by refactors. Do not rename variables, extract functions, restructure logic, or "clean up" adjacent code unless the task is explicitly about that. If you spot a real problem nearby, mention it — don't fix it.
- No reformatting. Never let an auto-formatter or your own habits reflow lines you didn't functionally change. Whitespace-only churn hides the real change in review.
- Clean up only your own mess. If your change makes an import, variable, or function unused, remove it. Do not remove pre-existing dead code unless asked.
- Preserve what works. Keep existing comments, error handling, and edge-case logic unless the task is to change them.
Before acting, ask yourself
> If a reviewer read this diff, would every changed line obviously connect to the request — or would they have to ask "why did you touch that?"
If any line would draw that question, revert it.
When the right fix IS a larger change
Sometimes the task genuinely requires broad changes (a real refactor, a migration). That's fine — but say so first: state what you're about to change and why it's in scope, then proceed. The rule isn't "never change a lot." It's "never change a lot silently."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: buildmoonshot
- Source: buildmoonshot/skillpacks
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.