Review and update all documentation — user docs, AGENTS.md — for accuracy, clarity, and freshness
From balatro-mod-devnpx claudepluginhub liafonx/open-balatro --plugin balatro-mod-dev/update-docsGenerates script references, env var docs from source files like package.json and .env.example, updates CONTRIBUTING.md and RUNBOOK.md, checks doc staleness, and shows update summary.
/update-docsUpdates implementation documentation: reviews specs/status/testing results, marks completed tasks, updates percentages, adds best practices/lessons to phase docs, CLAUDE.md, README.md.
/update-docsUpdates implementation documentation: reviews specs/status/testing results, marks completed tasks, updates percentages, adds best practices/lessons to phase docs, CLAUDE.md, README.md.
/update-docsSyncs documentation from package.json scripts and .env.example, generating docs/CONTRIB.md (dev workflow, scripts, env, testing) and docs/RUNBOOK.md (deployment, monitoring, issues, rollback). Identifies obsolete docs and shows diff.
/update-docsUpdates project docs: consolidates redundancies, debloats per style rules, detects AI slop, syncs capabilities, verifies accuracy via LSP. Supports --skip-* flags, --strict, --book-style.
/update-docsUpdates project documentation from source-of-truth files like package.json, .env.example, openapi.yaml, and Dockerfiles; generates script refs, env docs, contributing guide, runbook; checks staleness.
Review and update all documentation: user-facing docs, AI agent docs (AGENTS.md), and meta files.
README.md — Main documentation (English)README_zh.md — Main documentation (Chinese)CHANGELOG.md — Version history (English)CHANGELOG_zh.md — Version history (Chinese)docs/description.md — Concise README for quick referencedocs/NEXUSMODS_DESCRIPTION.txt — BBCode format for NexusModsAGENTS.md — Mod structure, functions, dependencies, dev status, constraints{ModName}.json — Check version numbermanifest.json — Check version number matchesgit worktree list 2>/dev/null
Exclude worktree directories from all file scans below.
# Find last release tag
git describe --tags --abbrev=0 2>/dev/null || echo "(no tags)"
# All commits since last release (use the tag found above)
git log <last-tag>..HEAD --oneline
# Files changed since last release
git diff <last-tag>..HEAD --stat
# If no tags exist, fall back to last 20 commits
git log --oneline -20
Read all files listed above AND the commit list. For each doc file, note:
Treat the commit list as the source of truth for what changed — docs should reflect every user-visible change.
Compare AGENTS.md against the actual codebase:
## Docs Audit Report
### Commits Since Last Release
- Last tag: [tag or "(no tags)"]
- Commits: [N commits — list user-visible changes]
- Undocumented changes: [list anything not yet reflected in docs]
### User Docs
- [file]: [status: OK / outdated / missing]
### AGENTS.md
- [section]: [status: OK / outdated / stale / verbose / duplicate]
### Meta Files
- Version consistency: [OK / mismatch: {details}]
Ask before applying: "Found {N} issues across docs. Proceed with updates?"
For each approved change:
## Docs Update Complete
### Changes Made
- [file]: [what changed]
### Skipped (user declined or not needed)
- [file]: [reason]