improve-codebase-architecture

Scan a codebase for module deepening opportunities and render findings as a visual HTML report.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill improve-codebase-architecture-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/improve-codebase-architecture
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill improve-codebase-architecture-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate shallow modules, leaky seams, and scattered logic that make testing and navigation painful. This Skill surfaces those architectural friction points and presents concrete deepening refactors as a visual report, so teams can decide what to fix first. ## Core Features & Use Cases - Architecture exploration: Uses an Explore sub-agent to walk the codebase, applying the deletion test and depth analysis to find shallow modules, leaking seams, and poor locality. - Visual HTML report: Generates a self-contained HTML file in the OS temp directory with Tailwind and Mermaid diagrams showing before/after visualizations, recommendation strength badges, and a top recommendation. - Guided design grilling: After the user picks a candidate, runs a grilling loop to refine the design, updates CONTEXT.md with new domain terms, and offers ADRs for load-bearing rejections. - Use Case: A team inherits a codebase where order processing logic is scattered across six thin wrappers. Run this Skill to get a report showing how to collapse them into one deep module, then grill through the new interface design. ## Quick Start Ask the assistant to review this codebase for architectural deepening opportunities and present the candidates as a visual 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 launch an Explore sub-agent that walks the codebase looking for modules whose interface is nearly as complex as their implementation. It applies the deletion test to each suspect: if deleting the module would concentrate complexity rather than move it, it is flagged as a deepening candidate.

What is a deep module versus a shallow module?▼

A deep module has a small interface hiding a substantial implementation, while a shallow module's interface nearly matches its implementation. The Skill uses this vocabulary from the companion codebase-design skill to evaluate every candidate it reports.

What output does the architecture review produce?▼

It writes a self-contained HTML file to the OS temp directory using Tailwind and Mermaid from CDNs. Each candidate gets a card with files, problem, solution, benefits, a before/after diagram, and a recommendation strength badge of Strong, Worth exploring, or Speculative.

Does the architecture review respect existing ADRs?▼

Yes, it reads ADRs in docs/adr/ before proposing candidates. If a candidate contradicts an existing ADR, it is only surfaced when the friction justifies reopening the decision, and the card is marked with a warning callout referencing the ADR.

What happens after I pick a refactoring candidate?▼

The Skill runs a grilling loop to walk the design tree covering constraints, dependencies, and the deepened module's shape. It updates CONTEXT.md with new domain terms and offers to record an ADR when you reject a candidate for a load-bearing reason.