Skip to main content
ClaudeWave
Skill133 estrellas del repoactualizado 17d ago

version-bump

The version-bump skill automates version incrementing for individual plugins in the Claude Code Handbook monorepo. Use it when preparing releases or when users request to bump major, minor, or patch versions. It maintains version numbers solely in each plugin's plugin.json file and provides a structured workflow for identifying current versions, selecting target plugins, executing the bump, and reporting results.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules /tmp/version-bump && cp -r /tmp/version-bump/.claude/skills/version-bump ~/.claude/skills/version-bump
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Version Bump Skill

Per-plugin version bumping for the Claude Code Handbook monorepo. Each plugin can have independent versions.

## When to Use This Skill

Trigger this skill when users mention:
- "bump version" or "bump the version"
- "increment version" or "update version numbers"
- Any mention of "major", "minor", or "patch" version changes

## Version Locations

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.

## Workflow Instructions

### Step 1: List Current Versions

Show current plugin versions:

```bash
python .claude/skills/version-bump/scripts/validate_versions.py
```

### Step 2: Ask User Which Plugin(s) to Bump

Ask the user:
1. Which plugin(s) to bump (can be multiple, or "all")
2. Which bump type: major, minor, or patch

### Step 3: Execute Version Bump

Run the script with the selected plugins:

```bash
# 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
```

### Step 4: Report Results

After successful completion, display:
- Plugins bumped with old → new versions
- Next steps for git commit

## CLI Reference

```bash
# 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
```

## Examples

### Example 1: Bump Single Plugin
```
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'"
```

### Example 2: Bump Multiple Plugins
```
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"
```

### Example 3: Bump All Plugins
```
User: "Bump all plugins patch version"

[Runs: python bump_version.py patch --all]

Claude: "Done! All 13 plugins bumped from their current versions."
```

## Notes

- The script does NOT create git commits - user handles version control
- Plugins can now have different versions (independent versioning)
- Changelog updates are manual - user maintains CHANGELOG.md as needed
update-component-referenceSkill

This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the website.

spec-drivenSkill

Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".

subagent-reviewSkill

Review changed code for reuse, quality, and efficiency using three parallel disposable subagents. This skill should be used when the user says "review", "simplify", "code review", or wants a one-shot code review without persistent reviewers.

team-reviewSkill

Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after review.

handbook-discoverSkill

This skill should be used when users want to discover, browse, or audit cc-handbook marketplace plugins. Shows all available plugins with installation status, versions, and component breakdown (skills, agents, commands, MCP/LSP servers, hooks). Trigger phrases include "discover plugins", "list handbook plugins", "what plugins are available", "browse marketplace".

coverage-reportSkill

Generate a .NET code coverage report scoped to files changed in the current branch. Runs tests with coverage collection and produces filtered HTML reports.

dotnet-dependencySkill

This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.

dotnet-run-fileSkill

Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.