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.
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-bumpSKILL.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
Analyze a task and produce an Architecture Decision Record with implementation steps.
Generate a .NET code coverage report scoped to files changed in the current branch. Runs tests with coverage collection and produces filtered HTML reports.
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.
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.
This skill should be used when working with Verify snapshot tests in .NET projects. Use when updating verified snapshots after intentional code changes, accepting new snapshots, discovering verify tests, or troubleshooting snapshot mismatches. Trigger phrases include "verify tests", "update snapshots", "accept snapshots", "verified files", ".verified.txt".
>
This skill should be used when the user wants to manage Git worktrees - creating worktrees from local or remote branches, listing active worktrees with details, deleting worktrees, or switching between worktrees. Ideal for working on multiple branches simultaneously without stashing changes.
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.