untangle-codebase
Skill1 starsChanged 26 days agoMITView on GitHub
Untangle a whole codebase in one pass, so agents working in it read less per change, break less without noticing, and debug faster.
8 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- raphaeldiscky/skillsedited, first seen Nov 16, 2026
- dedene/skillstheir own version, first seen Nov 15, 2026
- joemccann/radonedited, first seen Nov 9, 2026
- gustaferiksson/skillsedited, first seen Nov 8, 2026
- SwiftyJunnos/skillsedited, first seen Nov 8, 2026
- mneves75/skillstheir own version, first seen Nov 8, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- caldoai/skills★ 83199% same
- joemccann/radon★ 3484% same
- SwiftyJunnos/skills★ 199% same
- gustaferiksson/skills★ 099% same
- raphaeldiscky/skills★ 037% same
Wrote their own version · 3
- LordGhostX/agents-skills★ 19same name
- dedene/skills★ 15same name
- mneves75/skills★ 3same 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 repository121 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-agent-documentationSkill
- automate-meSkill
- babysit-and-shipSkill
- chief-of-staffSkill
- coordinatorSkill
- figure-it-outSkill
- git-guardrailsSkill
- learn-tasteSkill
- maintain-skillsSkill
- principlesSkill
- pstack-helpSkill
- pstack-modeSkill
- pstack-setupSkill
- recallSkill
- reflectSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- show-me-your-workSkill
- swarmSkill
- usage-reviewSkill
- wizardSkill
- writing-for-agentsSkill
- broSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- next-optionsSkill
- prSkill
- reply-shapeSkill
- teachSkill
- technical-writingSkill
- unslopSkill
- write-like-meSkill
- animateSkill
- animation-performanceSkill
- ask-sonnerSkill
- choreographSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- diagnosing-bugsSkill
- emil-design-engSkill
- gesturesSkill
- implementSkill
- implement-specSkill
- linting-alignmentSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-bot-uiSkill
- mobile-nativeSkill
- pstack-tddSkill
- remove-animationsSkill
- setup-agent-sign-inSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- statechartSkill
- tddSkill
- typescript-best-practicesSkill
- update-dependenciesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. 4 are common, 6 are distinctive, and 0 are very specific to this project.
4
Common
Most of the 8 edited versions we read keep these.
6
Distinctive
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 8
Start a thorough refactor of this codebase and complete it to the end.
- Distinctive: line 10
Treat this as a goal.
- Common: line 32
Don't change anything yet.
- Common: line 68
Ask the same thing of every fix, even one that looks better in the code: pieces that change together end up together, pieces that don't …
- Distinctive: line 70
Write each fix above the problems it solves, as in the decision log example.
- Distinctive: line 74
Remove the special cases the redesign makes unnecessary, and keep the ones the system still needs.
- Distinctive: line 76
If the user chose Comments:
- Common: line 82
If the user chose Tests, do this last, because tests are your regression safety net.
- Common: line 96
Every import is reasonable, and nothing imports anything more volatile than itself.
- Distinctive: line 106
Enter where leverage is highest: start looking there first.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Start a thorough refactor of this codebase and complete it to the end.
Treat this as a goal.
Why do this at all?
- Better output: agents write better code in a well-structured codebase.
- Cheaper & faster changes: agents spend fewer tokens searching and more on the problem.
- Fewer silent breaks: agents break less without noticing.
- Faster debugging: agents find root causes faster.
1. Ask
Besides untangling the codebase, there are two other things you may do:
| Addition | What it does |
| Comments | Remove comments that only restate the code. |
| Tests | Remove tests that wouldn't catch a real bug, and fix the ones that fail without one. |
List these (with their exact descriptions) for the user and ask which ones to do. Then do only those.
2. List every problem
Don't change anything yet.
Go through the codebase asking one thing: should these pieces change together? Write down every place the code gets the answer wrong, as in the decision log example. There are only three ways to get it wrong.
Hidden links: pieces that must change together, where the code doesn't show it.
- Copies of logic or values: change one and the others must change too, but nothing says so.
- A module that reads a global or file set by another module: change that module and this one breaks, but nothing shows it (self-contained code).
- A feature split across folders by layer, or related code in different folders: one change needs all of them, but the layout hides that (domain-driven code, colocation).
- A call order or convention callers just have to know: change it and callers break, but nothing warns them (explicit over implicit).
Needless links: pieces tied together that change for different reasons.
- Callers that depend on internals: the internals change for their own reasons, and the callers break anyway (encapsulation).
- Stable code that imports something more volatile: the stable code has to change whenever the volatile code does (dependency direction).
- A general function with a parameter only one workflow understands: the function has to change whenever that workflow does (caller vocabulary).
- A shallow module: its interface changes whenever its internals do, so its callers change with it (deep modules).
Surplus: pieces with no reason of their own to change.
- Wrappers: they only change when the thing they wrap does (pass-through wrappers).
- Extension points and config for things that never vary: nothing will ever change them (speculative generality).
- Dead code: nothing uses it, so nothing will ever need it to change.
Also write down every special case: code that exists for one situation instead of following from how the system works. Each one is a requirement the design never accounted for, so use them to work out what the system needs to be.
- An
iffor one value - A parameter for a specific caller
- A swallowed exception
- A retry or sleep
- A disabled test
3. Redesign from first principles
Work out the fixes as if the system had known today's requirements from the start. Look for the one fix behind several problems, which often looks nothing like them. Don't fix special cases one by one.
Ask the same thing of every fix, even one that looks better in the code: pieces that change together end up together, pieces that don't aren't tied, and everything depends on what changes less.
Write each fix above the problems it solves, as in the decision log example.
4. Fix everything on the list
Remove the special cases the redesign makes unnecessary, and keep the ones the system still needs. Don't go looking for bugs separately. A structural fix may fix some along the way, which is fine.
If the user chose Comments:
- Comments that restate the implementation, like
// sort first so the binary search works, only change when it does, so they have no reason of their own to change. Remove them, even if they're phrased as a why. - Comments about something outside the code, like
// the proxy drops websockets, so we poll, change when that does, and the code can't show it. Keep them. - Comments that explain a workaround om the codebase, like
// wait 100ms because the cache isn't ready yet, only change when the problem behind the workaround does. They go when the redesign removes that problem.
If the user chose Tests, do this last, because tests are your regression safety net. Invoke /principle-test-behavior-not-implementation for the test-quality criteria. A test should fail on a regression, and only then:
- Tests that repeat the implementation only change when it does, so they have no reason of their own to change. They check the same interpretation against itself, so remove them.
- Tests tied to internals break when the code changes but behavior doesn't, so they change for the wrong reason. Rewrite them to depend on behavior, which changes less.
- Tests that can't fail pass whatever the code does, so no change ever affects them. They aren't checking anything, so remove them.
5. Check, and repeat until done
Have subagents search for special cases, hidden links, needless links and surplus. Dispatch these and any other subagents through /swarm. Do not stop until there is nothing worth fixing left.
You're done when:
- As few special cases are left in the system as possible. How many remain is the best measure of how close you are.
- A typical change lands in one place.
- Every import is reasonable, and nothing imports anything more volatile than itself.
- Subagents have no issues left that are worth fixing.
- Intended behavior is the same as when you started, apart from bugs the refactor fixed. Test this at the end.
- /review-loop has run once, after everything above, as this workflow's final review of the whole refactor, from the commit the refactor started at. Each finding is fixed or reported to the user, and intended behavior is tested again after its fixes.
Tips
- Start from a skeleton: script away the function bodies, so the whole codebase fits in context.
- Summarize with subagents: have them summarize parts of the codebase, so you can reason across all of it at once.
- Check the dependency graph often: script one that shows what imports what, and rerun it as you go.
- Enter where leverage is highest: start looking there first.
- Keep a decision log: compaction is less of a problem that way.
- Use Git as evidence: for how often pieces change, and what changes together.
<a id="decision-log-example"></a>Decision log example
The list of problems:
- `ui/LogoutDialog.tsx:30` waits 100ms after closing and hopes the message input can take focus by then.
- `ui/Toolbar.tsx:40` and `ui/Menu.tsx:22` call the same actions, each with its own check for when they're disabled.
- `checkout/submit.ts:9` depends directly on `payments/stripe.ts`.
- `shortcuts/keymap.ts:18` has a switch with one case per action, separate from the menu's list.
- `ui/CommandPalette.tsx:55` keeps its own list of actions, and it's missing the newer ones.
- `ui/SettingsDialog.tsx:61` sets a global `skipRefocus` flag to stop the logout dialog it opens from sending focus to the message input.
- `history/undo.ts:30` has a special case for every action that can be undone.
- `refunds/refund.ts:22` wraps every Stripe call in `if (order.provider === "paypal")`.
- Every action handler has to call `track()` by hand, and some don't.
- `ui/Toolbar.test.tsx` and `ui/Menu.test.tsx` test the same actions separately.Then with the fixes:
- Make the general `Dialog` give focus back to whatever had it before it opened, so the wait and the flag can both go.
- `ui/LogoutDialog.tsx:30` waits 100ms after closing and hopes the message input can take focus by then.
- `ui/SettingsDialog.tsx:61` sets a global `skipRefocus` flag to stop the logout dialog it opens from sending focus to the message input.
- Define a `PaymentProvider` interface that Stripe and PayPal both implement, so checkout and refunds no longer know which one they're using.
- `checkout/submit.ts:9` depends directly on `payments/stripe.ts`.
- `refunds/refund.ts:22` wraps every Stripe call in `if (order.provider === "paypal")`.
- Make every user action a command with a name, a handler and an undo, so the toolbar, menu, shortcuts, palette and undo history all run from one list.
- `ui/Toolbar.tsx:40` and `ui/Menu.tsx:22` call the same actions, each with its own check for when they're disabled.
- `shortcuts/keymap.ts:18` has a switch with one case per action, separate from the menu's list.
- `ui/CommandPalette.tsx:55` keeps its own list of actions, and it's missing the newer ones.
- `history/undo.ts:30` has a special case for every action that can be undone.
- Every action handler has to call `track()` by hand, and some don't.
- `ui/Toolbar.test.tsx` and `ui/Menu.test.tsx` test the same actions separately.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.

