aide-untanglelisted
Install: claude install-skill ragnarwestad/aide
# Untangle a codebase
Find every place the code answers one question wrong — **should these
pieces change together?** — and every file or folder over the project's
size limits, and hand each fix over as spec text. The output is a map and
a list of specs; the code is left exactly as it was.
**Input:** $ARGUMENTS (an area or a concern to start from, or nothing for
the whole codebase)
## Ground rules
- **Change nothing.** No code, no tests, no docs, no specs, no git. Reading,
searching and running read-only scripts (a line count, an import graph,
`git log`) is allowed and expected. A fix that looks obvious is still
written down, not made: it goes through a spec, where it gets an
analysis, tests and a review.
- **Every finding has a `file:line`.** A finding without one cannot be
checked, and a spec built on it starts with a guess.
- **Verify before you write it down.** Open the file and read the lines.
A finding a search suggested and nobody read is the most common wrong
finding (see Pitfalls).
## Workflow
### Step 1: Agree on the area
Whole codebase, or the area in `$ARGUMENTS`. For more than a few hundred
files, say how you will split the reading (by top-level folder, by
module) and how long it will take, before you start. Subagents may read
parts in parallel; each one gets the brief in
[references/method.md](references/method.md), "Brief for a subagent",
and returns findings with `file:line`, never edits.
### Step 2: Check the size limits
The project's o