Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 69% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -2% | 0% |
| case-18 | ✗→✓ | ▲ Improved | -38% | 0% |
| case-05 | ✓→✗ | ▼ Worse | -81% | 0% |
| case-06 | ✓→✗ | ▼ Worse | -57% | 0% |
Invest in the shape of the system a little at a time rather than paying for a rewrite later. This skill diagnoses and proposes; it does not rewrite on its own.
modules, data flow, who calls whom. Reuse module-map for the one-screen view; do not skip to opinions.
its surface.
does.
domain-modeling - boundaries in codeshould track boundaries in the language).
relieves it: extract a boundary, collapse a duplicate, invert a dependency, move a seam. Prefer a sequence of safe steps over one big cut.
are safe now and which need a test net first (pair with tdd).
question, write a decision record in docs/decisions/NNNN-slug.md: context, choice, alternatives rejected, why.
any code moves.
reason.
for indirection unless the duplication actually drifts.
tests.
A prioritized list: each item is the problem, the smallest move, the risk, and whether it needs a test net first. Plus decision records for the big moves. No code changes until the user picks what to do.
Other measured skills in the registry, with their headline benchmark lift.