.claude/skills/documentation-updates/SKILL.md
Use after modifying library skills, library commands, or agents to ensure CHANGELOG, README, and docs are updated
npx skillsauth add axiomantic/spellbook documentation-updatesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Change | CHANGELOG | README | Docs Generator | |--------|-----------|--------|----------------| | Add library skill | "Added" section | count++, add table row, add link ref | Run | | Modify library skill | "Changed" section | Only if description changed | Run | | Remove library skill | "Removed" section | count--, remove row/link | Run | | Add/modify command | Appropriate section | Update if count/description affected | Run |
## [Unreleased]ls skills/*/SKILL.md | wc -l and ls commands/*.md | wc -lpython3 scripts/generate_docs.py executed## [Unreleased]
### Added
- **skill-name skill** - one-line description
- Notable feature bullet
### Changed
- **skill-name skill** - what changed and why
### Removed
- **skill-name skill** - removal rationale
[skill-name]: https://axiomantic.github.io/spellbook/latest/skills/skill-name/
<CRITICAL>
Library content (`skills/`, `commands/`, `agents/`) triggers this skill.
Repo content (`.claude/skills/`) does NOT.
</CRITICAL>testing
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Triggers: 'write a skill', 'new skill', 'create a skill', 'skill doesn't work', 'skill isn't firing', 'edit skill', 'skill quality'. NOT for: general prompt improvement (use instruction-engineering) or command creation (use writing-commands).
development
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for: reviewing existing plans (use reviewing-impl-plans).
testing
Use when creating new commands, editing existing commands, or reviewing command quality. Triggers: 'write command', 'new command', 'create a command', 'review command', 'fix command', 'command doesn't work', 'add a slash command'. NOT for: skill creation (use writing-skills).
development
Use when about to claim discovery during debugging. Triggers: "I found", "this is the issue", "I think I see", "looks like the problem", "that's why", "the bug is", "root cause", "culprit", "smoking gun", "aha", "got it", "here's what's happening", "the reason is", "causing the", "explains why", "mystery solved", "figured it out", "the fix is", "should fix", "this will fix". Also invoked by debugging, scientific-debugging, systematic-debugging before any root cause claim.