What problem does it solve? Repositories drift from canonical engineering conventions over time: labels diverge, config keys land in legacy namespaces, MCP wiring goes stale, cached plugin runtimes go missing, and dependency metadata desynchronizes. Manually auditing dozens of adoption checks across a repo is slow and error-prone, and unsafe auto-fixes can cause more damage than the drift itself. ## Core Features & Use Cases - Read-only diagnostic scorecard: Runs 30 checks covering label conformance, AGENTS/CLAUDE parity, config namespacing, statusline drift, MCP wiring, version coherence, workflow naming, runtime distribution, dependency-edge audits, host toolchain versions, and more — without mutating anything by default. - Gated --fix reconciliation: Applies each finding's canonical fix, batching safe idempotent repairs and requiring explicit per-item confirmation for hard-to-reverse changes like label renames, config migrations, and cache re-fetches. - Delegation to single-writer tools: Never hand-edits what another tool owns — version mismatches go to the release tool, setup gaps to /red-setup, and ticket authoring to /triage. - Use Case: Before launching a large autonomous /afk work drain, run the doctor to verify the repo's labels, hooks, runtime bundles, and toolchain all conform, then apply fixes with confirmation gates. ## Quick Start Ask the agent to run red doctor against this repository and report the adoption scorecard, optionally with --fix to apply the canonical fixes.
