deep-codebase-audit
Deep Codebase Audit
Surface architectural friction and propose deepening opportunities — refactors that turn shallow modules into deep ones. The aim is testability, AI-navigability, and leverage.
References for this skill are in the references/ folder:
- GLOSSARY.md — vocabulary to use in every suggestion
- DEPTH-GUIDE.md — how to classify dependencies and test across seams
- INTERFACES.md — how to explore alternative interfaces
When to Use
Use this skill when:
- The user says the codebase feels messy, hard to change, or "not ready for AI".
- You want to improve testability and make future TDD or autonomous agent work more effective.
- You're about to invest heavily in AI-driven changes and want to reduce risk first.
Do not use this skill when the user just wants to ship a small feature — use /incremental-tdd instead.
More from kambleakash0/agent-skills
english-humanizer
Detects and removes AI-generated writing patterns from English text. Rewrites content to sound natural, authentic, and genuinely human.
40grill-master
Relentlessly interview the user when they want to learn about a topic, plan, or design until you both reach a shared, testable understanding, before any planning or implementation.
15spec-writer
Create a comprehensive Product Requirements Document from conversation and repo context. Use when the user wants a PRD, product spec, feature requirements, or similar documentation.
13slice-the-spec
Turn a PRD into a Kanban-ready backlog of vertically sliced issues, with clear dependencies and HITL/AFK flags.
13git-workflow
>
13incremental-tdd
Test-driven development with a strict red-green-refactor loop, vertical slices, and deep modules. Use to build features or fix bugs using TDD.
13