improve-codebase-architecture

Scan a codebase for shallow modules and present deepening refactors as a visual HTML report.

1|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/taxmaxi/taxmaxi --skill improve-codebase-architecture-taxmaxi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/taxmaxi/taxmaxi/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/taxmaxi/taxmaxi --skill improve-codebase-architecture-taxmaxi

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 that architectural friction and proposes concrete deepening refactors instead of vague cleanup advice. ## Core Features & Use Cases - Architecture exploration: Walks the codebase (optionally via a sub-agent), weights recently changed hot spots from git history, and applies the deletion test to find shallow modules, leaky seams, and poor locality. - Visual HTML report: Renders each candidate refactor as a self-contained HTML file in the OS temp directory with Tailwind and Mermaid diagrams, before/after visualizations, recommendation-strength badges, and ADR conflict callouts. - Grilling loop: After the user picks a candidate, drives a decision-tree conversation about constraints, dependencies, and the deepened module's shape, keeping CONTEXT.md and ADRs current. - Use Case: Point it at a service whose handlers, validators, and repositories have multiplied into thin wrappers; it produces a report showing how to collapse them into one deep module with a single testable interface. ## Quick Start Ask the assistant to review this repository for architecture improvements and show the deepening candidates as 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 walk the codebase and apply the deletion test: if deleting a module would concentrate complexity rather than move it, the module is a deepening candidate. It weights recently changed files from git history so hot spots get attention first.

What does the architecture review report look like?▼

The report is a single self-contained HTML file written to the OS temp directory, styled with Tailwind via CDN and diagrammed with Mermaid plus hand-built SVG. Each candidate gets files, problem, solution, benefits, a before/after diagram, and a Strong, Worth exploring, or Speculative badge.

Does the review respect existing ADRs and architecture decisions?▼

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

Can I scope the architecture review to one module or subsystem?▼

Yes. If you name a direction such as a module, subsystem, or pain point, the Skill takes that scope directly. Otherwise it infers scope from commit history hot spots and widens the net when changes are scattered.

What happens after I pick a refactoring candidate?▼

The Skill enters a grilling loop that walks constraints, dependencies, the deepened module's shape, and which tests survive. It updates CONTEXT.md with new domain terms and offers to record an ADR when you reject a candidate for a load-bearing reason.