| name | doc-gardening |
| description | Cross-check docs/ against current code — flag stale file paths, broken cross-references, removed APIs, and outdated examples. Use when docs may have drifted after code changes. For doc completeness and quality use /documentation-audit instead. |
| user-invocable | true |
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:
- Read
CODEBASE_MAP.md for project understanding
- Read
CLAUDE.project.md if it exists for project-specific rules
- 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.
