Architecture Audit

Audits a codebase for shallow/coupled modules and writes a deep-module refactor PRD.

Autor: helderberto · helderberto/agent-skills

Działa po konfiguracji ★ 8.0/10

Architecture Audit — Audits a codebase for shallow/coupled modules and writes a deep-module refactor PRD.

Co robi ten skill

Explores a codebase for architectural friction (pass-through wrappers, temporal decomposition, tight coupling at seams) and writes an improvement PRD proposing a refactor toward deep modules (small interface, large implementation), with alternative interface designs and a migration plan. Triggers on requests to audit architecture or find structural friction across a codebase; explicitly not for single-module interface design or diff-level code review.

Raport z testu

SKILL.md leans on a sibling skill folder ('../codebase-design/SKILL.md' and its DEEPENING.md) for its core vocabulary and dependency-category logic -- copy just architecture-audit/ per the standard single-directory install and those links 404 locally. Ran a real audit against a 4-file throwaway app with a textbook pass-through service; the skill-guided run produced a genuinely more actionable deliverable than an unaided baseline -- a full improvement-template.md PRD (problem/interface/dependency-strategy/migration/risks) vs. the baseline's two throwaway sentences.

Testowano: 2026-07-15 · Claude Code 2.x (agent harness)

Instalacja

git clone https://github.com/helderberto/agent-skills
mkdir -p ~/.claude/skills
cp -r agent-skills/skills/architecture-audit ~/.claude/skills/architecture-audit
cp -r agent-skills/skills/codebase-design ~/.claude/skills/codebase-design   # required sibling dependency, see notes

Komendy i przykładowe prompty

  • /architecture-auditAudits a codebase for shallow/coupled modules and writes a deep-module refactor PRD.

Skille uruchamiają się na zwykłe polecenia — bez komend do zapamiętania. Po instalacji aktywują go prompty takie jak te (po angielsku):

  • Audit this codebase for architectural friction and propose a refactor
  • Find the shallow, pass-through modules coupling this service together
  • Write a PRD proposing deeper module boundaries for this messy repo