- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add aiskillstore/marketplace --skill untangle-codebase -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add aiskillstore/marketplace --skill untangle-codebase -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add aiskillstore/marketplace --skill untangle-codebase -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add aiskillstore/marketplace --skill untangle-codebase -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/aiskillstore/marketplace/tree/HEAD/pending/caldoai/untangle-codebaseDo publicador
Start a thorough refactor of this codebase and complete it to the end.
Treat this as a goal.
Why do this at all?
1. Ask
Besides untangling the codebase, there are two other things you may do:
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.
Needless links: pieces tied together that change for different reasons.
Surplus: pieces with no reason of their own 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.
if for one value3. 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:
// 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.// the proxy drops websockets, so we poll, change when that does, and the code can't show it. Keep them.// 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. A test should fail on a regression, and only then:
5. Check, and repeat until done
Have subagents search for special cases, hidden links, needless links and surplus. Do not stop until there is nothing worth fixing left.
You're done when:
Tips
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.
Untangle a whole codebase in one pass, so agents working in it read less per change, break less without noticing, and debug faster.
---name: untangle-codebasedescription: Untangle a whole codebase in one pass, so agents working in it read less per change, break less without…---# pending/caldoai/untangle-codebase/SKILL.mdPerguntas frequentes
Baixe pending/caldoai/untangle-codebase/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/aiskillstore/marketplace.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.