improve-codebase-architecture

Scan a codebase for module deepening opportunities and render findings as a self-contained HTML report.

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

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 presents concrete deepening refactors as visual before/after diagrams. ## Core Features & Use Cases - Scoped exploration: Uses commit history hot spots or a user-named direction to focus the scan, applying the deletion test to identify shallow modules, seam leakage, and poor locality. - Visual HTML report: Writes a single self-contained HTML file (embedded CSS, inline SVG, no JavaScript or network dependency) to the OS temp directory, with before/after diagrams, recommendation-strength badges, and a top recommendation. - Decision grilling loop: After the user picks a candidate, walks constraints, dependencies, and interface shape via companion skills, updating the domain glossary and living important-decisions document as decisions crystallize. - Use Case: Point it at a subsystem where changes keep bouncing between many small files; it produces a report showing which modules to collapse into one deep module with a single testable interface. ## Quick Start Ask the assistant to review the architecture of the order intake subsystem and show 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 scan the codebase for modules whose interface is nearly as complex as their implementation. It applies the deletion test — asking whether deleting a module would concentrate complexity — and renders each finding as a before/after diagram in an HTML report.

How to generate an architecture review report as HTML?▼

The Skill writes a single self-contained HTML file to the OS temp directory using embedded CSS and inline SVG diagrams. It requires no JavaScript, network access, or package installation, and each run produces a fresh timestamped file.

Does the architecture review modify my repository files?▼

Exploration is read-only local inspection, and the report is written to the OS temp directory so nothing lands in the repo. Only domain glossary or important-decisions documents are updated later, and only as decisions crystallize during the grilling loop.

What vocabulary does the architecture review use?▼

It uses a fixed glossary from the companion codebase-design skill: module, interface, implementation, depth, seam, adapter, leverage, and locality. Terms like component, service, API, or boundary are deliberately avoided to keep recommendations consistent.

When should I not run an architecture deepening review?▼

Skip it when a candidate contradicts a living important decision without real friction to justify revisiting it, or when changes are scattered with no hot spots and no user-named direction. The Skill scopes by recent change activity because deepening only pays off where future changes will occur.