Purpose
This audit system provides one repeatable command for repository-wide docs health:
- performance hotspots (scripts/report footprint)
- route/link integrity and legacy path drift
- stale or placeholder content risk
- UK English and style consistency for English
v2 docs
- component-layout governance by page type
- conservative cleanup recommendations with quarantine-first workflow
Default Operating Mode
Use static and report-synthesis mode first. It is faster, deterministic and safe for routine use.
node tools/scripts/repo-audit-orchestrator.js --mode static --scope full
The AI-tools registry is the canonical inventory/lifecycle surface for ai-tools/**, but the audit system still uses its existing subsystem-specific catalog and manifest below.
Inputs:
ai-tools/registry/ai-tools-registry.json (AI-tools inventory + lifecycle reference)
ai-tools/ai-skills/catalog/skill-catalog.json
ai-tools/ai-skills/catalog/execution-manifest.json
docs.json
- existing reports under
tasks/reports/
Outputs:
tasks/reports/repo-ops/repo-audit-summary.json
tasks/reports/repo-ops/repo-audit-summary.md
- per-stage reports in
tasks/reports/repo-ops/
Policy Defaults
- Cleanup: classify only by default; no deletion; quarantine only when explicitly requested.
- Language: enforce EN-GB style in English
v2 pages in phase 1.
- Agent portability: generate packs from one source catalog.
Entry Points
- Orchestrator:
tools/scripts/repo-audit-orchestrator.js
- Pipeline manifest:
ai-tools/ai-skills/catalog/execution-manifest.json (audit subsystem only)
- Skill catalogue:
ai-tools/ai-skills/catalog/skill-catalog.json (audit subsystem only)
- Global AI-tools registry:
ai-tools/registry/ai-tools-registry.json
Last modified on March 16, 2026