chore(concepts-checklist): add Rule 9 (bundled skill/command rename tracking)
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -67,3 +67,11 @@ Rules for verifying CONCEPTS table accuracy. Each rule is checked during every w
|
||||
- **Source to compare against**: Official docs page body (mechanism/"how it works" sections)
|
||||
- **Date added**: 2026-05-21
|
||||
- **Origin**: Checkpointing Location read `automatic (git-based)` for every prior run, but `/en/checkpointing` explicitly states checkpoints track file-editing-tool changes (not git, not bash) and are "not a replacement for version control" — *"checkpoints as 'local undo' and Git as 'permanent history'."* Existing rule #5 (Description Currency) only inspects the Description column, so a factual error in the Location column went unchecked indefinitely
|
||||
|
||||
### 9. Bundled Skill / Command Rename Tracking
|
||||
- **Category**: Description Accuracy (Location column)
|
||||
- **What to check**: Any slash command or bundled skill named in a CONCEPTS/Hot **Location** column (e.g. `/simplify`, `/code-review`, `/loop`, `/batch`, `/goal`, `/ultrareview`) still exists under that exact name — i.e. it was not renamed or removed in a recent version
|
||||
- **Depth**: Scan the last N versions of the CHANGELOG for "renamed", "removed", or "deprecated" command/skill events; cross-check the current `/en/commands` reference and the `/en/skills#bundled-skills` list for the actual current command names
|
||||
- **Source to compare against**: `https://raw.githubusercontent.com/anthropics/claude-code/main/CHANGELOG.md` + `https://code.claude.com/docs/en/commands` + `https://code.claude.com/docs/en/skills#bundled-skills`
|
||||
- **Date added**: 2026-05-25
|
||||
- **Origin**: `/simplify` was renamed to `/code-review` in v2.1.147 — a **changelog-only event** that the docs-page-listing checks (rules #1/#3) and the claude-code-guide 95-concept sweep both missed; only a raw-CHANGELOG read caught it. Rules #5/#8 inspect Location *characterization* against docs page bodies but don't systematically scan the changelog for command renames, so a renamed command in a Location column could persist indefinitely
|
||||
|
||||
Reference in New Issue
Block a user