Who it is forA developer maintaining a tangled codebase that agents have been speeding up into more complexity.
The problemAgent-driven coding accelerates software entropy, so the design drifts faster than anyone reviews it.
The outcomeA visual HTML report of candidate deepening opportunities and a grilled plan for the one you choose.
What you need first
- A coding agent that supports the plugin or skills install route, such as Claude Code or Codex
- A project repository the agent can read and edit
- Optional: an issue tracker such as GitHub or GitLab, or a local folder for tickets
Steps
- Install the plugin in Claude Code with
claude plugin install mattpocock-skills@claude-plugins-official. - Run
/improve-codebase-architectureon your repo. - Open the HTML report and pick one candidate.
- Let the agent grill you through the chosen candidate before it changes any code.
Prompt for your agent
In the mattpocock/skills repo, run improve-codebase-architecture on <repo path>. Expected output: an HTML report of deepening candidates, then a grilling session on the one I pick. Verify that the report lists concrete modules rather than general advice.
Caveat. This is a survey, not a rescue: on a genuinely old codebase it finds real candidates but will not untangle the mud for you.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page