aped-arch-audit

Audit codebases for shallow interfaces and output ranked architecture reports.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-arch-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-arch-audit
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-arch-audit
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-arch-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you find parts of an existing codebase that are hard to evolve because their interfaces are shallow and mirror their implementation, which lowers leverage and weakens locality.

Core Features & Use Cases

  • Surfaces deepening candidates without refactoring: identifies modules where consolidation and interface deepening would reduce caller complexity and concentrate change.
  • Enforces the deletion test discipline: distinguishes true pass-through wrappers from modules that earn their keep by reappearing across call sites.
  • Ranks candidates with vocabulary-consistent reasoning: uses module/interface/seam/adapter/leverage/locality terms and produces an audit report that HALTs for explicit user validation.

Quick Start

Run the aped-arch-audit skill with an optional scope like src/auth to generate architecture-audit.md listing ranked deepening candidates.

Frequently Asked Questions about aped-arch-audit

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

FAQPage Schema
How do I audit my codebase architecture to find shallow modules that need deepening?

An architecture audit for module deepening surfaces interfaces that mirror their implementation, lowering leverage and weakening locality. It applies the deletion test to distinguish pass-through wrappers from modules earning their keep, producing a ranked report of refactor candidates.

What is the deletion test when evaluating module refactor opportunities?

The deletion test evaluates refactor opportunities by distinguishing true pass-through wrappers from modules that earn their keep. It checks whether a module reappears across multiple call sites, confirming its leverage and locality before recommending interface deepening.

How do I identify deepening opportunities in source code without auto-refactoring?

Identify deepening opportunities without auto-refactoring by scanning for shallow interfaces and applying the deletion test. This surfaces consolidation candidates that reduce caller complexity and concentrate change, halting for explicit validation before generating a ranked audit report.

Does an architecture audit work on specific source directories like src/auth?

Yes, the architecture audit works on specific source directories like src/auth. Running the audit with an optional scope parameter generates a targeted architecture-audit.md report listing ranked deepening candidates within that boundary.

Why does low locality and leverage make existing codebases hard to evolve?

Low locality and leverage make codebases hard to evolve because shallow interfaces mirror implementation details, spreading change across multiple call sites. Deepening these module interfaces concentrates change and reduces caller complexity, improving overall architecture adaptability.