| name | source-command-audit-audit |
| description | One-pass health audit — runs doctor, a tech-debt sweep, and a QA status check; summarizes top actions. |
source-command-audit-audit
Use this skill when the user asks to run the migrated source command audit.
Command Template
🔎 Audit
Run a consolidated health check of the project and summarize the most important
actions. Good to run weekly or before a release (and a natural fit for a
scheduled/recurring run — see below).
- Install health —
node contextkit/tools/scripts/doctor.mjs — report any ✗
critical issues or ⚠ notes.
- Metrics —
node contextkit/tools/scripts/stats.mjs — note drift rate and
cadence; flag if drift is high (sessions not being registered).
- Tech debt —
node contextkit/tools/scripts/tech-debt-scan.mjs --quick — list
the worst offenders; interpret which are real (don't fix here).
- Contract — if
l5.contractGlobs is set,
node contextkit/tools/scripts/contract-scan.mjs — flag removed/renamed exports.
- QA status — if a test suite exists, run it (and coverage if available) and
note whether
qa.criticalPaths are covered vs qa.coverageTarget.
- Drift — note any unregistered prior sessions or stale claims from boot.
Output a single prioritized list: 🔴 do now / 🟡 soon / 🟢 fyi, each with the
file and the one-line fix — this is the audit report.
Feed the backlog so nothing is lost. Ingest the mechanical findings (run
tech-debt-scan.mjs --write first, then node contextkit/tools/scripts/pipeline.mjs ingest contextkit/memory/tech-debt-findings.json --type chore), and pipeline.mjs add the 🔴/🟡 items you raised by judgment (🔴→P0/P1, 🟡→P2). The priorities are
auto-assigned but always editable by the user (`pipeline.mjs prioritize
` or `/pipeline`). Offer to open a focused `/dev-start` on the top item.
Tip: to run this on a schedule, use the harness — e.g. /loop for an interval
in-session, or /schedule to register a recurring remote agent that runs
/audit (and pings you with the result).
