Skip to content
bump-version logo

Bump Version Skill

bump-version

This skill should be used when the user wants to bump the version number in the workspace. It updates versions across all pyproject.toml files (root, tde, and tda packages) and the CHANGELOG.md to keep them synchronized.

mattnigh/skills_collection0installs24stars

SKILL.md

Full skill instructions

Bump Version Skill

Update package versions and changelog across the workspace using semantic versioning.

Purpose

Bump package versions in the uv workspace by updating all pyproject.toml files (root workspace, tde, and tda packages) and CHANGELOG.md simultaneously. This ensures all packages maintain version synchronization and changelog is updated for the release.

When to Use

Use this skill when:

  • User requests to "bump the version"
  • User asks to "update version to patch/​minor/​major"
  • User wants to increment the package version
  • Version needs to be updated before a release

Usage

Execute the bump_version.py script from the workspace root with the bump type:

python .claude/​skills/​bump-version/​scripts/​bump_version.py <major|minor|patch>

Bump Types

  • major: Increment major version (1.0.0 → 2.0.0), reset minor and patch to 0
  • minor: Increment minor version (1.0.0 → 1.1.0), reset patch to 0
  • patch: Increment patch version (1.0.0 → 1.0.1)

What Gets Updated

The script updates:

  1. Root pyproject.toml (workspace) - version field
  2. src/​tde/​pyproject.toml (Tech-Debt Extractor package) - version field
  3. src/​tda/​pyproject.toml (Tech-Debt Agent package) - version field
  4. CHANGELOG.md - Creates new version section from [Unreleased] content

All pyproject.toml files are kept in sync with the same version number. The CHANGELOG.md has the [Unreleased] section converted to a dated version section, with a new empty [Unreleased] section added above it.

Examples

Bump patch version (0.1.0 → 0.1.1):

python .claude/​skills/​bump-version/​scripts/​bump_version.py patch

Bump minor version (0.1.0 → 0.2.0):

python .claude/​skills/​bump-version/​scripts/​bump_version.py minor

Bump major version (0.1.0 → 1.0.0):

python .claude/​skills/​bump-version/​scripts/​bump_version.py major

Workflow

  1. Before bumping: Ensure CHANGELOG.md has changes documented in the [Unreleased] section

    • Add entries under appropriate categories (Added, Changed, Fixed, etc.)
    • Follow Keep a Changelog format
  2. Ask user for bump type: Use AskUserQuestion tool to clarify which version bump to perform

    AskUserQuestion(
        questions=[{
            "question": "Which version bump should be performed?",
            "header": "Version bump",
            "options": [
                {"label": "Patch", "description": "Bug fixes and minor changes (0.1.1 → 0.1.2)"},
                {"label": "Minor", "description": "New features, backward compatible (0.1.1 → 0.2.0)"},
                {"label": "Major", "description": "Breaking changes (0.1.1 → 1.0.0)"}
            ],
            "multiSelect": false
        }]
    )
    
  3. Execute script: Run with the user-confirmed bump type

    python .claude/​skills/​bump-version/​scripts/​bump_version.py <patch|minor|major>
    
  4. Verify changes: Check that all files were updated correctly

    • All three pyproject.toml files should have the new version
    • CHANGELOG.md should have a new dated section for the version
    • New empty [Unreleased] section should be at the top
  5. Update changelog with recent changes: After the version bump, automatically update the [Unreleased] section

    • Use git status and git diff --stat to review what changed in the repository
    • Check for new files in .claude/ or other directories
    • Update CHANGELOG.md [Unreleased] section with appropriate entries under categories:
      • Added: New files, features, or functionality
      • Changed: Modifications to existing functionality
      • Removed: Deleted files or removed functionality
    • Document the changes clearly and concisely
    • Example entries:
      • - Claude Code settings configuration (.claude/​settings.json)
      • - Reorganized bump-version skill to follow Claude Code structure
  6. Provide instructions to user: Display the following instructions for completing the release:

    To complete the version bump:
    
    1. Review the changes:
       git status
       git diff CHANGELOG.md
    
    2. Commit the version bump:
       git add .
       git commit -m "chore: bump version to X.Y.Z"
    
    3. Create a git tag:
       git tag vX.Y.Z
    
    4. Push changes and tag:
       git push origin main
       git push origin vX.Y.Z
    

    Replace X.Y.Z with the actual version number that was bumped to.

Changelog Management

The CHANGELOG.md follows Keep a Changelog format:

  • [Unreleased]: Work-in-progress changes (gets converted to version section when bumping)
  • Categories: Added, Changed, Deprecated, Removed, Fixed, Security

When bumping a version, the script:

  1. Finds the [Unreleased] section
  2. Converts it to a dated version section (e.g., ## [0.1.2] - 2025-01-10)
  3. Adds a new empty [Unreleased] section at the top

Important: Always document changes in [Unreleased] before bumping. The bump process doesn't add changelog entries—it only converts existing unreleased entries into a versioned section.

More skills from mattnigh

spring-framework-patterns logo
mattnigh/skills_collection

spring-framework-patterns

Comprehensive Spring Framework and Spring Boot best practices including dependency injection patterns, bean lifecycle and scopes, REST API development, Spring Data JPA, service layer design, Spring Security, testing strategies, caching, AOP, async processing, error handling, and common anti-patte...

24 0
View

TypeScript厳格モードによる型安全性設計を専門とするスキル。 📖 参照書籍: - 『Effective TypeScript』(Dan Vanderkam): 型設計 📚 リソース参照: - `resources/Level1_basics.md`: レベル1の基礎ガイド - `resources/Level2_intermediate.md`: レベル2の実務ガイド - `resources/Level3_advanced.md`: レベル3の応用ガイド - `resources/Level4_expert.md`: レベル4の専門ガイド - `resources/di...

24 0
View
deploying-cloud-k8s logo
mattnigh/skills_collection

deploying-cloud-k8s

Deploys applications to cloud Kubernetes (AKS/GKE/DOKS) with CI/CD pipelines. Use when deploying to production, setting up GitHub Actions, troubleshooting deployments. Covers build-time vs runtime vars, architecture matching, and battle-tested debugging.

24 0
View
moai-alfred-agent-guide logo
mattnigh/skills_collection

moai-alfred-agent-guide

19-agent team structure, decision trees for agent selection, Haiku vs Sonnet model selection, and agent collaboration principles. Use when deciding which sub-agent to invoke, understanding team responsibilities, or learning multi-agent orchestration.

24 0
View
mermaid-diagram-generator logo
mattnigh/skills_collection

mermaid-diagram-generator

Converts architecture descriptions, module specs, or workflow docs into Mermaid diagrams. Use when visualizing brick module relationships, workflows (DDD, investigation), or system architecture. Supports: flowcharts, sequence diagrams, class diagrams, state machines, entity relationship diagrams,...

24 0
View
pre-flight-check logo
mattnigh/skills_collection

pre-flight-check

INVOKE FIRST before any code work. Validates git workflow (branch, issue, worklog) and checks approach. Use at START of every task and END before completing. Prevents skipped steps.

24 0
View
browser-dev-tools logo
mattnigh/skills_collection

browser-dev-tools

This skill should be used when working with browser-rendered artifacts (i.e. Bun, React/React Native) to proactively validate that development work on localhost is being built appropriately and to support debugging browser-rendered content. Use this skill after making frontend changes to verify t...

24 0
View
lead-dev logo
mattnigh/skills_collection

lead-dev

Lead Développeur - Coordination technique opérationnelle, code review, mentoring et livraison. Pair de web-dev-process au niveau OPÉRATIONS.

24 0
View
worker-monitor logo
mattnigh/skills_collection

worker-monitor

Monitor Docker workers, RQ queue health, and auto-scale workers (max 4). Use when: checking job progress, monitoring queue depth, scaling workers up/down, diagnosing slow processing, or waiting for jobs to complete. Referenced by data-quality skill during reprocessing.

24 0
View
quality-advisor logo
mattnigh/skills_collection

quality-advisor

Proactive quality guidance system that monitors artifact creation and provides real-time feedback on documentation quality

24 0
View
check-code-quality logo
mattnigh/skills_collection

check-code-quality

Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.

24 0
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View