// This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
Analyze a Claude Code session for "wrong-turn" moments (corrections, retries, waste, reversals, dead-ends) and produce an interactive HTML dashboard with copy-able recommendations (CLAUDE.md rules, docs, scripts, hooks, memory entries, sub-skills, etc.) that would help future agents reach the goal faster. Defaults to reflecting on the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /reflect or asks to learn from this session.
Summarize WHAT WAS SHIPPED in a Claude Code session as a self-contained HTML slide deck — the elevator pitch (problem, solution, decisions, artifacts, verification, gaps), not a play-by-play of tool calls or debugging detours. Defaults to the current in-context session; optionally accepts a session ID or JSONL path. Renders directly in the reflect aesthetic — no delegation. Use when the user invokes /reflect-solution or asks for a recap deck of what changed.
Visualize a Claude Code session as a quest/skill tree — a navigable SVG graph where nodes are turns and edges show flow, with distinct visual encoding for normal flow, dead-ends, corrections, retries, reversals, and backtracking. Sibling to /reflect (which produces an incidents+recommendations dashboard); this one shows the journey itself. Defaults to the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /reflect-tree or asks to map a session as a tree/graph/journey.
Analyze a task and produce an Architecture Decision Record with implementation steps.
Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation. Use when the user says "team stack", "create a team", "set up agents for this", or describes a complex task that would benefit from multiple agents working together.
| name | version-bump |
| description | This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository. |
Per-plugin version bumping for the Claude Code Handbook monorepo. Each plugin can have independent versions.
Trigger this skill when users mention:
Single source of truth: plugins/<name>/.claude-plugin/plugin.json
The marketplace.json is a lightweight registry (no version field) — versions live only in plugin.json.
Show current plugin versions:
python .claude/skills/version-bump/scripts/validate_versions.py
Ask the user:
Run the script with the selected plugins:
# Single plugin
python .claude/skills/version-bump/scripts/bump_version.py <bump_type> --plugin <name>
# Multiple plugins
python .claude/skills/version-bump/scripts/bump_version.py <bump_type> --plugin <name1> --plugin <name2>
# All plugins
python .claude/skills/version-bump/scripts/bump_version.py <bump_type> --all
After successful completion, display:
# Show help
python .claude/skills/version-bump/scripts/bump_version.py --help
# Error + list plugins when no --plugin flag
python .claude/skills/version-bump/scripts/bump_version.py patch
# Bump specific plugin(s)
python .claude/skills/version-bump/scripts/bump_version.py patch --plugin handbook-dotnet
python .claude/skills/version-bump/scripts/bump_version.py minor --plugin handbook --plugin handbook-extras
# Bump all plugins (legacy monorepo behavior)
python .claude/skills/version-bump/scripts/bump_version.py patch --all
User: "Bump the version for handbook-dotnet"
Claude: "I'll check current versions first..."
[Runs validate_versions.py]
Claude: "handbook-dotnet is currently at 1.19.5. What bump type: major, minor, or patch?"
User: "patch"
[Runs: python bump_version.py patch --plugin handbook-dotnet]
Claude: "Done!
handbook-dotnet: 1.19.5 → 1.19.6
Next steps:
1. git diff
2. git add . && git commit -m 'chore: bump handbook-dotnet to 1.19.6'"
User: "Bump handbook and handbook-extras to a new minor version"
[Runs: python bump_version.py minor --plugin handbook --plugin handbook-extras]
Claude: "Done!
handbook: 1.19.5 → 1.20.0
handbook-extras: 1.19.5 → 1.20.0"
User: "Bump all plugins patch version"
[Runs: python bump_version.py patch --all]
Claude: "Done! All 13 plugins bumped from their current versions."