doc-gardeninglisted

# Doc Gardening ## Core Rule Flag drift, never silently rewrite. A doc may be intentionally aspirational; the human decides whether to update the doc or the code. This skill produces a punch list — the human applies the fix. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections (Top Rules + index) If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/doc-gardening` when: - The codebase has shifted (rename, refactor, feature removal) and you suspect docs lag behind - After a major release, to sweep `docs/` and `README.md` for stale references - As a scheduled background task (`/loop weekly /doc-gardening`) to keep drift bounded - Before publishing a release or onboarding a new contributor ## Default Behavior When the user asks to audit, scan, review, or "give me a report" for doc drift, produce the full doc-gardening report automatically using the Process and Output Format sections below. Do not require the user to specify fields. Only modify files when the user explicitly requests implement / fix / apply / refactor. By default, this skill is **report-only**. ## Scope This skill covers: - `docs/` (all `*.md` files) - `README.md` at repo root - `CODEBASE_MAP.md` at repo root - `tasks/lessons/_index.