surgical-change
Skill0 starsChanged 25 days agoMITView on GitHub
Implement a small feature or bounded bug fix with minimal files and a focused diff. Use for scoped implementation; not for broad redesigns, read-only reviews, or release operations.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- songjiun10-collab/Senior-thinking-skillstheir own version, first seen Oct 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- songjiun10-collab/Senior-thinking-skills★ 87same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acceptance-qaSkill
- architecture-reviewSkill
- bug-fix-verificationSkill
- dependency-upgradeSkill
- docs-syncSkill
- idea-to-scopeSkill
- implementation-planSkill
- independent-reviewSkill
- migration-safetySkill
- performance-investigationSkill
- pull-request-handoffSkill
- release-checkpointSkill
- root-cause-investigationSkill
- security-reviewSkill
- test-gap-auditSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Inspect: Read the entry point, affected implementation, nearby tests, and project-specific instructions.
- Distinctive: line 17
Implement: Follow existing conventions.
- Distinctive: line 18
Verify: Run the smallest useful checks first, then nearby checks if practical.
- Distinctive: line 24
Do not stage, commit, push, release, deploy, or mutate external systems unless explicitly authorized.
- Distinctive: line 25
Do not update dependencies or regenerate large artifacts just because a tool suggests it.
- Distinctive: line 26
Remove only dead code/imports caused by this change unless broader cleanup was requested.
- Distinctive: line 27
Do not claim an outcome is verified when checks were skipped, failed, or only simulated.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Surgical change
Objective
Deliver the requested behavior with the narrowest correct modification and explicit verification. This workflow implements code; it is not an independent review.
Steps
- Inspect. Read the entry point, affected implementation, nearby tests, and project-specific instructions. Confirm what is already working.
- Bound the task. State a one-sentence outcome and a small set of observable acceptance criteria. Identify in-scope files and explicit exclusions when useful.
- Handle uncertainty. Choose and disclose a narrow reversible assumption for harmless ambiguity. Stop before a decision affecting security, production, external authority, credentials, data loss, or irreversible state.
- Implement. Follow existing conventions. Prefer direct changes over additional layers, configuration, or dependencies. Keep unrelated code untouched.
- Verify. Run the smallest useful checks first, then nearby checks if practical. For a bug, prefer evidence of prior failure and subsequent success when available.
- Inspect. Review changed paths and full diff for incidental changes, weakened validation, or unexplained formatting. Check worktree state.
- Report. Summarize behavior changed, verification evidence, test gaps, assumptions, and unrelated observations without fixing them opportunistically.
Boundaries
- Do not stage, commit, push, release, deploy, or mutate external systems unless explicitly authorized.
- Do not update dependencies or regenerate large artifacts just because a tool suggests it; explain necessity before expanding scope.
- Remove only dead code/imports caused by this change unless broader cleanup was requested.
- Do not claim an outcome is verified when checks were skipped, failed, or only simulated.
Output
A concise handoff with scope, change, evidence, and limitations. Cite actual commands/results where available; never invent passing tests.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

