improve-codebase-architecture

Identifies shallow modules and proposes deepening refactors rendered as an HTML architecture review report.

2|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/Nzettodess/Awesome-Agent-Skills --skill improve-codebase-architecture-nzettodess
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/Nzettodess/Awesome-Agent-Skills/tree/main/Skills/Engineering%20Skills/skills/engineering/improve-codebase-architecture
Command: npx skills add https://github.com/Nzettodess/Awesome-Agent-Skills --skill improve-codebase-architecture-nzettodess

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, navigate, and reason about. This Skill surfaces that architectural friction and proposes concrete deepening refactors grounded in the project's own domain language and recorded ADR decisions. ## Core Features & Use Cases - Architecture exploration: Walks the codebase with an Explore sub-agent to find shallow modules, leaking seams, and tightly-coupled clusters, applying the deletion test to validate candidates. - HTML review report: Renders candidates as a self-contained HTML file with Tailwind and Mermaid before/after diagrams, recommendation-strength badges, and a top recommendation section. - Grilling loop and interface design: After the user picks a candidate, runs a design conversation that updates CONTEXT.md, offers ADRs for rejected candidates, and spawns parallel sub-agents to design alternative interfaces. - Use Case: A team inherits a service where order processing logic is scattered across six thin wrappers. Run this Skill to get a visual report showing how to collapse them into one deep module with a single testable interface. ## Quick Start Ask the agent to review this repository for architectural deepening opportunities and produce an HTML report of the candidates.

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 refactoring opportunities in a large codebase?▼

Run this Skill to explore the codebase with an Explore sub-agent that looks for shallow modules, leaking seams, and pass-through wrappers. It applies the deletion test to each candidate and renders findings as an HTML report with before/after diagrams.

What is a deep module versus a shallow module?▼

A deep module hides a large amount of behaviour behind a small interface, giving callers leverage and maintainers locality. A shallow module has an interface nearly as complex as its implementation, so it adds indirection without hiding complexity.

Does the architecture review write files into my repository?▼

No. The HTML report is written to the OS temp directory as architecture-review-<timestamp>.html and opened in your browser, so nothing lands in the repo. CONTEXT.md and ADR files are only updated during the grilling loop when design decisions crystallize.

How does the skill handle existing ADRs that conflict with a suggestion?▼

Candidates that contradict an existing ADR are only surfaced when the friction is real enough to warrant revisiting the decision. The report marks them with a warning callout referencing the ADR rather than listing every theoretically forbidden refactor.

Can I explore alternative interface designs for a proposed refactor?▼

Yes. After picking a candidate, the Skill can spawn three or more parallel sub-agents that each design a radically different interface under distinct constraints, then presents and compares them by depth, locality, and seam placement with an opinionated recommendation.