skills.rest
pxlcrtiv
pxlcrtivCOMMUNITY
Explore all skills by this author →
GitHub

improve-codebase-architecture

Identify architectural weaknesses in codebases and generate an HTML report.

Updated Jul 3, 2026
Search Tags:#refactoring#software design#codebase analysis#code architecture#HTML report
One-click install
npx skills add https://github.com/pxlcrtiv/opencode-setup --skill improve-codebase-architecture-pxlcrtiv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/pxlcrtiv/opencode-setup/tree/main/skills/improve-codebase-architecture
Command: npx skills add https://github.com/pxlcrtiv/opencode-setup --skill improve-codebase-architecture-pxlcrtiv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies architectural weaknesses in a codebase, presents them visually, and guides users through refactoring for better depth and locality.

Core Features & Use Cases

  • Codebase Scanning: Identifies shallow modules and architectural friction points.
  • Visual HTML Report: Generates an interactive HTML report highlighting candidates for refactoring.
  • Grilling Loop: Facilitates discussion and decision-making through an iterative design process.
  • Use Case: Use this Skill to uncover and address issues in a complex codebase, such as overly shallow modules or leaky seams, leading to more maintainable and testable code.

Quick Start

Run the 'improve-codebase-architecture' skill to start analyzing your codebase.

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 architectural weaknesses in a complex codebase?▼

This Skill scans your codebase to identify architectural weaknesses like shallow modules and friction points, then visualizes these structural issues in an interactive HTML report to guide your refactoring decisions.

What is the best way to visualize code architecture for refactoring?▼

The best way to visualize code architecture for refactoring is generating an interactive HTML report that highlights shallow modules and friction points, allowing you to clearly see where structural improvements are needed.

How do I plan refactoring decisions for modules with poor depth and locality?▼

You plan refactoring decisions for poor module depth and locality by using an iterative grilling loop that facilitates design discussion, helping you systematically evaluate and address architectural friction points.

Can I analyze a codebase with multiple modules and dependencies?▼

Yes, you can analyze a codebase with multiple modules and dependencies, as this Skill is specifically designed to uncover architectural weaknesses and leaky seams in complex, multi-module codebases.

When do I need to refactor shallow modules in software design?▼

You need to refactor shallow modules in software design when they create architectural friction and leaky seams that reduce maintainability, as increasing module depth and locality leads to more testable code.

Related Skills

Explore More Software Engineering Skills→
raphaelmansraphaelmans

improve-codebase-architecture

Analyze codebases to surface architectural friction and generate deepening RFCs.

Community
Advanced
ThorStarlordThorStarlord
1

improve-codebase-architecture

Identify codebase refactoring opportunities using the deletion test and ADR-aware candidate framing.

Community
Advanced
Ni-BuNi-Bu
4

improve-codebase-architecture

Identify architectural friction and refactoring opportunities in codebases.

Community
Advanced
TrecekTrecek
1

design-guards

Parse bug pattern audit reports and design architectural guards with tests and contracts.

Community
Advanced