claude-md-doctor

# CLAUDE.md Doctor — exam procedure You are running a checkup on this repository's agent-instruction files. The deterministic work lives in scripts; your job is the judgment between them. Do not re-derive what a script already measured, and do not skip a stage — the report verifies the work-state manifest and will disclose skipped stages. Definitions used below: - `SCRIPTS` = `${CLAUDE_SKILL_DIR}/scripts` — Claude Code substitutes `${CLAUDE_SKILL_DIR}` with this skill's own directory at run time, so the scripts resolve no matter the working directory or how the skill was installed. Use it literally; do not try to locate the skill yourself. - `REPO` = the repository to examine (the argument if one was given, else the current working directory). - `WORK` = `REPO/.claude-md-doctor/work` (scripts default to this; pass `--work` to relocate, e.g. into a scratch directory to avoid writing in the user's repo — prefer that when the repo is not yours to dirty). ## Stage 0 — preflight Run `python3 --version`. If python3 is missing, stop and tell the user this skill needs Python 3.9+ (stdlib only, nothing to install). ## Stage 1 — intake python3 SCRIPTS/intake.py --repo REPO --work WORK Then read `WORK/intake.json` (it is small). Note for later judgment: - Is the project CLAUDE.md a **pointer** (`is_pointer`) to AGENTS.md? That is the healthy, officially-recommended pattern — the target is the patient. Never diagnose a pointer file as "too short." Check `pointe...