| name | phx-audit |
| description | Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors. |
Project Health Audit
Comprehensive project-wide health assessment across five independent concern tracks.
Usage
/skill:phx-audit # Full audit (default)
/skill:phx-audit --quick # 2-3 minute pulse check
/skill:phx-audit --focus=security # Deep dive single area
/skill:phx-audit --focus=performance
/skill:phx-audit --since abc123 # Incremental audit since commit
/skill:phx-audit --since HEAD~10 # Audit last 10 commits
When to Use
- Quarterly health checks
- Before major releases
- After large refactors
- New team member onboarding (understand codebase health)
Iron Laws
- Complete every selected track before synthesizing — partial results make
cross-category scores misleading
- Scope each track to concrete directories and checks — vague project-wide
analysis produces generic findings
- Never compare scores across projects — track trends only within the same
codebase
- Run quick mode before full mode — catch basic failures before expensive
analysis
Portable Audit Workflow
- Create
.claude/audit/reports/ and .claude/audit/summaries/.
- Run the quick checks below. Stop and report a blocker when the project cannot
compile or its test command cannot start.
- Complete five tracks: architecture, performance, security, tests, and
dependencies. Native generic workers may run independent tracks in parallel
when the runtime provides them; otherwise run every track sequentially in
this session. Never require named custom agents.
