improve-codebase-architecture

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

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill improve-codebase-architecture-tajo9128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/tajo9128/BioDockify-Pharma-AI/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill improve-codebase-architecture-tajo9128

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, presented visually rather than as a wall of prose. ## Core Features & Use Cases - Architecture exploration: Uses an Explore sub-agent plus git history hot-spot analysis to find shallow modules, seam leakage, and poor locality, applying the deletion test to validate candidates. - Visual HTML report: Writes a self-contained Tailwind + Mermaid HTML report to the OS temp directory with before/after diagrams, recommendation-strength badges, and ADR conflict callouts. - Decision grilling loop: After the user picks a candidate, runs a grilling workflow that updates CONTEXT.md, offers ADRs for rejected candidates, and supports design-it-twice interface exploration. - Use Case: Point it at a subsystem that keeps changing, review the rendered report of deepening candidates, pick one, and walk the decision tree until the refactor shape is settled. ## Quick Start Ask the assistant to review the architecture of the current codebase and show deepening opportunities 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 with an Explore sub-agent, weighting recently changed files from git history. It flags modules whose interface is nearly as complex as their implementation and validates each candidate with the deletion test.

What is a deepening refactor in software architecture?

A deepening refactor turns a shallow module into a deep one: a small interface hiding a substantial implementation. The Skill presents each candidate with before/after diagrams showing how collapsing wrappers concentrates complexity and improves testability.

Where does the architecture review report get saved?

The report is written as a self-contained HTML file to the OS temp directory, resolved from $TMPDIR with fallback to /tmp or %TEMP%, named architecture-review-<timestamp>.html. Nothing is written into the repository itself.

Does the architecture review respect existing ADRs?

Yes. The Skill reads ADRs in docs/adr/ before proposing candidates and avoids re-litigating recorded decisions. It only surfaces a contradicting candidate when the friction justifies reopening the ADR, marked with a warning callout.

What happens after I pick a refactoring candidate?

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