Refactor
Make the same change across many files safely. Use when renaming a symbol, changing a call signature, moving a pattern, or applying a consistent edit to a whole codebase.
Install
$ agentstack add skill-1aifanatic-super-computer-refactor ✓ 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-1aifanatic-super-computer-refactor) 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
Systematic multi-file edits
The danger in a refactor is not the edit, it is the edit you did not know you needed to make. Find the full blast radius before changing anything.
Always, in this order
- Enumerate.
grep -rn "oldName" /workspace— every occurrence, before touching one. - Count.
grep -rc "oldName" /workspaceper file, so you know when you are done. - Classify. Definitions, call sites, imports, strings, comments and tests need different treatment. A blind replace corrupts the ones that are not code.
- Edit with
edit_file, one occurrence at a time with enough surrounding context to be unique. - Verify.
grep -rn "oldName" /workspaceagain. Zero results, or only the ones you deliberately left.
Use editfile, not writefile
Rewriting a file to change one line bills the whole file as output tokens and risks losing anything you did not carry across. edit_file fails loudly when old_string is not unique, which is a feature: that error is telling you the change is ambiguous and needs more context.
When a change genuinely is uniform across a file, replace_all is correct — but check the count first so you know what you are agreeing to.
Partial-word traps
grep matches substrings. Renaming user will also hit username, userId and superuser. Anchor the pattern:
grep -rnw "user" /workspace
grep -rn "\buser\b" /workspaceThe limit you must state
You cannot run the tests, the build, or the type checker. A refactor that looks complete is unverified. When you finish, say so plainly — "renamed 14 occurrences across 6 files; not compiled or tested" — rather than implying the change is known good.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: 1aifanatic
- Source: 1aifanatic/super-computer
- 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.