improve-codebase-architecture

Identify shallow modules and weak seams to prioritize deep refactoring candidates.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill improve-codebase-architecture-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/lgwanai/openforce/tree/main/skills/improve-codebase-architecture
Command: npx skills add https://github.com/lgwanai/openforce --skill improve-codebase-architecture-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve a codebase by identifying architectural friction where modules are shallow, seams are weak, or testing cannot reliably target behavior, so refactors concentrate complexity and increase leverage.

Core Features & Use Cases

  • Surfaces deepening opportunities by analyzing module interfaces, dependency categories, and where understanding repeatedly leaks across seams.
  • Guides refactoring toward depth using the interface as the test surface, applying the deletion test to prioritize high-leverage changes.
  • Supports informed follow-ups with a “grilling loop” to crystallize constraints, dependencies, seams, adapters, and test strategy, and can optionally explore alternative interface designs.

Quick Start

Use the improve-codebase-architecture skill to identify deepening candidates in your project and propose refactors that improve testability and AI-navigability.

Frequently Asked Questions about improve-codebase-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor shallow modules into deep, testable ones?

Identify deepening opportunities by analyzing module interfaces and dependency categories where understanding repeatedly leaks across weak seams. This surfaces friction in shallow modules, guiding refactors that concentrate complexity and increase architectural leverage.

What is the best way to find weak seams and poor interface locality in a codebase?

Diagnose weak seams and poor interface locality by analyzing dependency categories and module interfaces using the seam-and-adapter vocabulary. This highlights areas where testing cannot reliably target behavior and understanding leaks across boundaries.

How do I improve codebase architecture for AI-navigability and testability?

Improve codebase architecture for AI-navigability and testability by guiding refactors toward depth using the interface as the test surface and applying the deletion test. This prioritizes high-leverage changes that concentrate complexity and increase leverage.

How do I prioritize refactoring candidates when planning architecture reviews?

Prioritize refactoring candidates during architecture reviews by applying the deletion test to high-leverage changes and using a grilling loop. This crystallizes constraints, dependencies, seams, adapters, and test strategy to produce prioritized candidates with clear problem, solution, and benefits.

Can I use seam and adapter patterns to diagnose dependency issues in my code?

Use the seam and adapter vocabulary to diagnose dependency issues by analyzing where understanding repeatedly leaks across seams and where testing cannot reliably target behavior. This supports informed follow-ups and optionally explores alternative interface designs.