docs-updatelisted
Install: claude install-skill TsukiNi22/ai-utils
# Update all the documentation
Goal: after changes, **nothing that describes the project is stale** - docs, site, wiki, packages, install scripts,
version strings. Think of every place the project is described, not only the README.
## 1. Baseline: what changed
Find what the docs must catch up with, in this order:
1. What the user says changed (the request, the conversation).
2. The pending diff (`\git status`, `\git diff HEAD`) and the commits since the **last docs update** or the last
release: `\git describe --tags --abbrev=0`, `\git log <tag>..HEAD --oneline`,
`\git log -1 --format=%H -- README.md CHANGELOG.md docs`.
3. The **latest version**: the source of truth is the code (`project(... VERSION x.y.z)`, `pyproject.toml`,
`package.json`, `Cargo.toml`, `reference/VERSION.md`, the last tag, a `version` constant). Take the newest one
found, and report any disagreement between them. For a dependency documented from its upstream (ex: libutils),
take its latest release (`libutils` skill: `scripts/update.sh`).
Run `scripts/inventory.sh [repo]` for the first pass: it lists the documentation surfaces that exist, the
versions found, dead links in the Markdown and what is not committed yet.
## 2. Inventory every surface that exists
Check each one; skip what the project has not. Do not stop at the first hit.
| Surface | What to bring up to date | Skill |
|---|---|---|
| `README.md` (+ sub-READMEs of tools / modules) | features, tables, command lists, install, usage