Menu
Audit every ai/ file for gaps, stale placeholders, and inconsistencies after cold-start. Produces a prioritized findings report.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULE_MAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULE_MAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
Deep, judgement-based adversarial code audit — hunts for stale cross-references, unescaped interpolation, platform gaps, generated-file ownership conflicts, and cross-module consistency rot that no mechanical check can catch. Read-only; writes a dated findings report.
Kit-maintainer diagnostic (LOCAL-ONLY, not distributed) that audits the README and docs/ for staleness against the repo's real command/skill/CLI roster, stamped tree, and cross-doc consistency. Read-only; produces a severity-ranked findings report.
Run verification and drift checks on the AI knowledge-base to identify missing documentation or stale references.
Deep-mine the source code to discover implemented features; writes ai/analysis/FEATURE_CATALOG.md.
| name | post-cold-start-verification |
| description | Audit every ai/ file for gaps, stale placeholders, and inconsistencies after cold-start. Produces a prioritized findings report. |
| disable-model-invocation | true |
Audit the AI knowledge layer. Read-only with one exception: you may write ONE report.
If ai/analysis/audit-reports/VERIFICATION_MANIFEST.json exists, read its summary
and the non-confirmed claims first: path-existence checking is already done
deterministically by the kit's verify command (run from the kit checkout:
node install.mjs verify <repo> — no LLM
involved, so its statuses are facts). Spend your pass on what a script cannot
judge (checks 1, 3, 4 below, and the semantic half of check 2). If the manifest
is absent or older than the docs it covers, recommend regenerating it in your
report instead of re-deriving path checks by hand.
<fill in>, ? Stability, and {{...}} leftover
across ai/ and the entry files (CLAUDE.md, AGENTS.md).ai/guide/* exists on disk
(covered by the manifest when present — see Step 0); MODULE_MAP rows correspond
to real directories; FEATURE_MAP entries point at real files; diagrams name
real modules.ai/repo-profile.json; flag divergence (don't silently fix).[verified] tag lacking a date; nothing you can tell
was agent-written carrying [verified].Write ai/analysis/audit-reports/<YYYY-MM-DD>-post-cold-start.md: findings grouped
P1 (agent-blocking) / P2 (misleading) / P3 (cosmetic), each with location and a
one-line suggested fix. Tag the report itself [inferred]. Do not modify the files
you are auditing.