improve-codebase-architecture

Analyze codebase module depth and generate HTML architecture reports.

110|4|Updated Jul 19, 2016
One-click install
npx skills add https://github.com/deathbeam/dotfiles --skill improve-codebase-architecture-deathbeam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/deathbeam/dotfiles/tree/main/agents/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/deathbeam/dotfiles --skill improve-codebase-architecture-deathbeam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses architectural friction by identifying shallow modules that lack depth and locality, helping you refactor them into robust, testable, and AI-navigable components.

Core Features & Use Cases

  • Architectural Review: Scans the codebase to identify shallow modules and leaky abstractions.
  • Visual Reporting: Generates a self-contained HTML report featuring Mermaid diagrams and custom SVG visualizations to illustrate deepening opportunities.
  • Design Guidance: Enforces a strict architectural vocabulary (module, interface, depth, seam, adapter, leverage, locality) to ensure consistent design language across the team.

Quick Start

Run the improve-codebase-architecture skill to generate an architectural review report for the current repository and identify potential refactoring 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 identify shallow modules and refactoring opportunities in my codebase?

A codebase architecture review involves scanning your repository to identify shallow modules and leaky abstractions. This skill analyzes module depth, interface surface area, and dependency leakage to locate architectural friction and propose structural refactors.

How can I generate visual architecture diagrams for my codebase?

You can generate visual architecture diagrams by analyzing module depth and dependency leakage to produce static HTML reports. This skill uses Tailwind and Mermaid to create self-contained visualizations that illustrate architectural deepening opportunities and design improvements.

What is the best way to visualize dependency leakage and modularity issues?

The best way to visualize dependency leakage is by generating custom SVG visualizations and Mermaid diagrams within a static HTML report. This skill maps interface surface area and dependency leakage to propose structural refactors that improve modularity and testability.

Does this codebase architecture review require any specific dependencies or external tools?

No external dependencies are required. The skill operates independently to analyze your repository and generates a self-contained static HTML report using Tailwind and Mermaid, requiring no additional environment setup to identify architectural friction.

When should I not use automated architectural refactoring reports?

You should avoid automated architectural refactoring reports when your codebase lacks established modules or clear interface boundaries. The skill relies on analyzing existing module depth and interface surface area to identify architectural friction and propose structural refactors.