improve-codebase-architecture

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

1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill improve-codebase-architecture-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/jwh3times/holland-vip --skill improve-codebase-architecture-jwh3times

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 proposes concrete deepening refactors, so you can decide what to fix with evidence instead of gut feel. ## Core Features & Use Cases - Hot-spot-driven exploration: Scopes the scan using recent git history and user direction, then applies the deletion test to find shallow modules, leaked seams, and missing locality. - Visual HTML report: Generates a self-contained Tailwind + Mermaid report in the OS temp directory with before/after diagrams, recommendation-strength badges, and ADR conflict callouts for each candidate. - Guided decision loop: After you pick a candidate, it runs a grilling workflow to refine constraints and interfaces, updating CONTEXT.md and offering ADRs as decisions crystallize. - Use Case: Point it at a subsystem where bugs keep recurring; it identifies that the order intake pipeline is shallow, renders a before/after diagram showing the collapse into one deep module, and walks you through the refactor decision. ## Quick Start Ask the assistant to review this codebase for architecture improvements and show the 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 architecture improvement opportunities in my codebase?▼

Run this Skill to scan your codebase for shallow modules, leaked seams, and missing locality. It scopes the search using recent git history hot spots, then presents each candidate as a before/after diagram in an HTML report.

How to visualize refactoring candidates before committing to them?▼

The Skill writes a self-contained HTML report to your OS temp directory using Tailwind and Mermaid from CDNs. Each candidate gets a side-by-side before/after diagram, a recommendation-strength badge, and a one-sentence problem and solution.

Does the architecture review respect existing ADRs?▼

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

What happens after I pick a refactoring candidate?▼

The Skill runs a grilling loop that walks the decision tree with you: constraints, dependencies, the deepened module's shape, and surviving tests. It updates CONTEXT.md with new domain terms and offers to record load-bearing rejections as ADRs.

When should I not use automated architecture scanning?▼

Skip it when the codebase has no meaningful git history to identify hot spots, or when you already know the exact change needed. The Skill is designed for exploratory deepening decisions, not executing a predetermined refactor.