Individual skill
architecture-audit
Surface architectural friction across a codebase and propose deep-module refactors as RFCs.
skills/architecture-audit/SKILL.md
Source commit ced546848ec8eea8541e77b7aa041207b607462e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 20
- Repository last updated
- Oct 26, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- skills Repository topic
- cursor Repository topic
- antigravity Repository topic
- claude-code Repository topic
- agents Repository topic
- codex Repository topic
- engineering Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,072 bytesreferences/deep-modules.mddoc · 2,850 bytesreferences/html-report.mddoc · 2,649 bytesreferences/improvement-template.mddoc · 1,237 bytes
Read excerpt
# Architecture Audit
Audit a codebase for architectural friction and propose refactors toward **deep modules** (simple interface, large implementation). Deep modules are more testable, more AI-navigable, and let you test at the seam instead of inside.
Uses the deep-module vocabulary and principles — call the Skill tool with `codebase-design` for the canonical glossary (module, interface, depth, seam, adapter, leverage, locality) and core principles (deletion test, interface-as-test-surface, one-adapter-is-hypothetical). Use those terms exactly in every suggestion. For audit-specific examples and anti-patterns (pass-through, temporal decomposition, classitis, signs a module is too shallow), see [references/deep-modules.md](references/deep-modules.md).
## Workflow
### 1. Explore
**Scope first (YAGNI).** Deepening pays off where code keeps changing. A direction in `$ARGUMENTS` (module, subsystem, pain point) → take it. Otherwise read a good stretch of `git log --oneline` for hot spots, the files and areas that keep coming up, and start there; no clear hot spot → widen the net. Read the ADRs in the area: a candidate an ADR already rejected comes back only when the friction is worth reopening it.
Use a read-only explore subagent to navigate the codebase organically. Note where you experience friction:
