improve-codebase-architecture

Identify architectural friction and rank shallow module deepening opportunities.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/bartolomeomueller/hr --skill improve-codebase-architecture-bartolomeomueller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/bartolomeomueller/hr/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/bartolomeomueller/hr --skill improve-codebase-architecture-bartolomeomueller

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This process helps teams identify architectural friction in a codebase and surface opportunities to deepen shallow modules to improve maintainability, testability, and AI-navigable exploration.

Core Features & Use Cases

  • Explore the codebase to surface tightly-coupled boundaries and actionable refactoring opportunities.
  • Present a prioritized list of deepening candidates with context, dependencies, and expected impact.
  • Use during architecture reviews and onboarding to guide targeted improvements.

Quick Start

Explore the repository to identify shallow modules suitable for deepening and present three renovation 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 during a codebase architecture review?

To identify shallow modules during an architecture review, explore the codebase to surface tightly-coupled boundaries and testing bottlenecks. This process ranks deepening candidates by presenting clusters, dependency categories, and expected test impact.

What is the best way to refactor a codebase to improve testability?

The best way to refactor a codebase for testability is to deepen shallow modules to reduce coupling. By surfacing architectural friction and generating design RFCs, you can target specific boundary definitions and testing bottlenecks for renovation.

How do I find architectural friction and coupling in a codebase?

You find architectural friction by performing code exploration to analyze boundary definitions and dependency categories. The process identifies tightly-coupled areas and outputs ranked deepening opportunities with clusters to guide refactoring.

Can I generate a design RFC for refactoring shallow modules?

Yes, you can generate a design RFC for refactoring shallow modules. The process coordinates codebase exploration, candidate presentation, and RFC generation to document deepening opportunities, dependencies, and expected test impact.

Does this architecture review process work for onboarding to a new codebase?

Yes, this architecture review process works for onboarding to a new codebase. Exploring the codebase to surface coupling and boundary definitions helps new developers understand architectural friction and identify deepening opportunities.