claude-sdk-rs: Command for Claude Code

Update Docs — Documentation health sweep: find stale sections and create missing coverage.

Audits the entire documentation set against the current codebase and recent git history. Produces a structured gap report (stale sections, missing coverage, confirmed-current). Optionally fixes STALE sections and creates MISSING docs with --patch, or skips the audit and creates all missing docs from scratch with --bootstrap.

This is the ad-hoc maintenance counterpart to /document (which gates on sdlc/state.json's recorded review.verdict being PASS, not a prose report — see /document's Record section). Use /update-docs for periodic doc health checks and bootstrapping outside the SDLC pipeline; use /document inside it.

Variables

$ARGUMENTS — optional flags:

• --patch — after the audit, (1) apply surgical fixes for clear-cut STALE sections, and (2) create new docs for MISSING capabilities flagged by the audit. Conservative: only creates user-facing docs the audit confidently identifies.
• --bootstrap — skip the audit; create all missing project docs from scratch based on the current codebase state. Use on new projects or after large blocks with no prior doc coverage. Reads source, creates files, updates docs/index.md.
• --since <ref> — limit git history to commits after this ref (default: last 20 commits)
• A bare git ref/range (e.g. HEAD~10, main..HEAD) also sets the history window

Instructions

Phase 1 — Git history snapshot

1. Run git log --oneline -20 (or --since <ref> if provided) to understand what changed recently.
2. Run git diff HEAD~10 --stat (or the specified range) to see which source files shifted.
3. Note any new commands, engine flags, schema fields, or decision records added since the last doc update. These are the primary staleness signals.

Phase 2 — Codebase inventory

Sweep the source of truth for each documentation area. For each area, note: what exists now vs. what the docs claim.