improve-codebase-architecture

Scan a codebase for module deepening opportunities and present them as a visual HTML report.

2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill improve-codebase-architecture-moofonli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/MoofonLi/dev-ready/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill improve-codebase-architecture-moofonli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate shallow modules whose interfaces are nearly as complex as their implementations, making them hard to test and navigate. This Skill surfaces those architectural friction points and proposes concrete deepening refactors grounded in a shared design vocabulary. ## Core Features & Use Cases - Hot-spot-driven exploration: Scopes the review using git history and user direction, then explores the codebase for shallow modules, seam leakage, and poor locality. - Visual HTML report: Renders each candidate refactor as a self-contained HTML file with Tailwind and Mermaid before/after diagrams, recommendation-strength badges, and ADR conflict callouts, written to the OS temp directory. - Grilling loop: After the user picks a candidate, walks the decision tree via the /grilling skill, keeping CONTEXT.md and ADRs current through /domain-modeling. - Use Case: A team notices their order intake flow is spread across six thin wrappers. Run this Skill to get a visual report of deepening candidates, pick one, and grill through the design before writing any code. ## Quick Start Ask the agent to run the improve-codebase-architecture skill to review the current codebase and show architectural deepening candidates in an HTML report.

Frequently Asked Questions about improve-codebase-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find shallow modules in my codebase?

Run this Skill to explore the codebase for modules whose interface is nearly as complex as their implementation. It applies the deletion test to candidates and presents each finding with a before/after diagram in an HTML report.

How to generate a visual architecture review report?

The Skill writes a self-contained HTML file to the OS temp directory using Tailwind and Mermaid from CDNs, then opens it in your browser. Each candidate refactor gets a card with files, problem, solution, benefits, and a side-by-side before/after diagram.

Does the architecture review respect existing ADRs?

Yes, it reads ADRs in docs/adr/ before scanning and avoids re-litigating recorded decisions. A candidate that contradicts an ADR is only surfaced with a clear warning callout when the friction justifies reopening the decision.

What happens after I pick a refactoring candidate?

The Skill runs the /grilling skill to walk the decision tree covering constraints, dependencies, and the deepened module's shape. It also updates CONTEXT.md via /domain-modeling and can offer to record rejections as ADRs.

When should I not use this architecture review approach?

Skip it when the codebase has no clear hot spots and changes are trivially scattered, or when you need immediate interface proposals rather than exploration. The Skill deliberately does not propose interfaces until after the grilling loop.