update-docs

Run /update-docs with a description of the new tool. The Skill reads the git diff, pulls accurate syntax from the tool's README or help output, adds an entry to tools/overview.md, and optionally creates a dedicated tool page.

The Skill updates docs/public/index.json whenever new pages are created, then validates that every file path in the manifest points to an actual file and that every markdown file has a manifest entry.

No. It only modifies files under docs/public/. Internal docs such as docs/CodingStyle.md and docs/VisualStyle.md are explicitly excluded from updates.

The Skill never guesses at command syntax or options. It reads the actual source material, including docs/CC_TOOLS.md, tool README files, and the tool's own --help output, before writing documentation.

Use it when code changes affect public docs, such as new tools, features, or installation steps. It is also triggered after /review-code flags missing documentation. Manual writing suits large narrative content outside the docs/public/ structure.