Axidify Audit
Two modes — pick from the user's ask:
| Mode | Trigger | Output |
|---|---|---|
| Brief status | "status", "what's next", /status |
≤12 lines, no gap table |
| Feature audit | "what's implemented", gap analysis, /audit |
Evidence-backed gap table |
Not this skill: reviewing a diff before commit → review.
Brief status (≤12 lines)
- Current state — 1–2 sentences
- Branch / tree — branch; dirty working tree if relevant (
git status) - Recent changes — session work or last few commits
- Next 3 priorities — ordered
- Blockers — if any
For feature-level gaps with code references, switch to feature audit below.
Feature audit checklist
- Apply discover-project if needed
- Search broadly: feature name, routes, models, tests, permissions, jobs — not only one folder
- Per capability: Implemented, Partial, UI only, Backend only, Not implemented, Unknown
- Every claim needs a code reference (path, symbol, or line)
- Walk the main end-to-end flow as the code actually runs
- Gap table:
| Feature | Current | Expected | Gap | Priority | - If the project uses
docs/status/, offer to create or update[module]-status.md
Optional passes
- Test coverage map for the module
- Deprecated APIs, TODO/FIXME density in scope
Verification rules
- No reference → not implemented
- Uncertain → unknown — do not guess
- Do not infer backend from UI alone or UI from schema alone
Related skills
- discover-project — ground in repo layout first
- document — update
docs/status/when the project uses it - test — map test coverage for the module
- plan — next implementation steps after brief status