← AI Library
Skill · Curated · Review & QA
Improve codebase architecture
by Matt Pocock · reviewed by Mike Reams
Scans a codebase for shallow modules, shows the candidates in a visual report, then interviews you about the one you pick.
What you get
A report of the places where a refactor would put more behaviour behind a smaller interface, and a worked plan for the one you choose.
- When to use it
- When a codebase is hard to test or hard to find your way around, and before a larger refactor.
- Ask for it like this
- “Find the deepening opportunities in this codebase and show me the report.”
- Limits
- My copy writes the report to the temp folder, not the repository, and gives you the path instead of opening it.
What I changed, and why I run it
- Two skills, one card: codebase-design is the vocabulary the review speaks in (module, interface, depth, seam).
- I made the report self-contained. Upstream it loaded two scripts from CDNs, with a loose diagram setting, and opened the file with a shell command; mine loads nothing.
- I run it when the same files keep coming up in fixes. It starts from the commit history, so it looks where the change is.
- architecture
- refactoring
- deep modules
- testability
Source
- Author
- Matt Pocock
- Licence
- MIT
- Reviewed at
- 59db609
This card also covers codebase-design (opens in a new tab), from the same repository at the same commit.
Reviewed 2026-10-29 Passed after edits: every file read by hand and checked for prompt injection, hidden text, network calls, shell execution and credential reads.
Not hosted here: get it from the author, at the commit I reviewed.
