Current verification scope
Claude Code: Current coverage, checks, and limits of the official-source comparison and automated validation.
Written and reviewed by Eric Han · Co-founder & CTO, reopt
2026-10-23 · Claude Code 2.1.308
Coverage
The two editions cover all 120 official slash rows, the terminal CLI tables, and 79 individual command guides. Aliases, conditional, removed, and experimental entries are labeled.
What is checked
- Compare full command declarations, aliases, arguments, and option rows.
- Check that the shared catalog, lists, detail blocks, and navigation agree.
- Check paired detail routes and the ordered six-section structure in both editions.
- Track releases separately from reference changes. The 2026-10-23 audit compared v2.1.299–308, 120 slash rows, 36 CLI rows, and 80 flag rows, including expanded
/claude-apisyntax, the/design consentand/design revokerow, and CLI/flag prose changes. - Model statements follow the Model configuration and Fast mode docs and the Opus 5.5, Sonnet 5.5, and Haiku 5.5 model pages and the Pricing page on platform.claude.com.
- Validate MDX, internal routes and anchors, and official links.
Limits of the review
Documentation comparison and static checks do not mean every command was executed on every OS, plan, or organization policy. Check the installed menu and effective settings. A minimum version is not inferred where the source does not state one. Items that appear only in the changelog are labeled as release-tracked. Subcommands missing from the CLI tables, such as claude plugin configure, fall under this rule, while the 2026-10-07 review confirmed that /doctor prompt-audit is now in the official Commands table. Where the changelog (v2.1.284) and the official docs (v2.1.283) give different versions, as for the auto mode starting default, both are kept. Feature introduction versions follow the changelog; an unlisted subcommand is not treated as an official table entry.
The earlier full link audit could not read some npm and Claude routines pages because of access restrictions. Those limits remain recorded in the earlier audit.
Find earlier evidence
Dated audit records · Per-command version evidence · Release coverage history