Claude Code Plugins

Community-maintained marketplace

Feedback

Publish a new version of klaude-code to PyPI. This skill handles version bumping, changelog updates, git tagging, and package publishing. Use when the user wants to release a new version.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name publish
description Publish a new version of klaude-code to PyPI. This skill handles version bumping, changelog updates, git tagging, and package publishing. Use when the user wants to release a new version.

Publish Skill

This skill manages the release process for klaude-code, including version management, changelog updates, git tagging, and PyPI publishing.

Prerequisites

  • UV_PUBLISH_TOKEN environment variable must be set for PyPI publishing
  • Working directory must be the klaude-code repository root
  • Git repository must be clean (no uncommitted changes)

Release Workflow

Step 1: Determine Version Bump Type

Ask the user which version bump type to apply:

  • major - Breaking changes (X.0.0)
  • minor - New features, backwards compatible (x.Y.0)
  • patch - Bug fixes, backwards compatible (x.y.Z)

Step 2: Run Version Bump Script

Execute the version bump script to update pyproject.toml:

uv run .claude/skills/publish/scripts/bump_version.py <bump_type>

The script will:

  1. Read current version from pyproject.toml
  2. Calculate new version based on bump type
  3. Update pyproject.toml with new version
  4. Output the old and new version numbers

Step 3: Update CHANGELOG.md

Execute the changelog update script:

uv run .claude/skills/publish/scripts/update_changelog.py <new_version>

The script will:

  1. Get commits since the last tag
  2. Categorize commits by type (feat, fix, refactor, etc.)
  3. Update CHANGELOG.md with the new version section
  4. Move [Unreleased] changes to the new version

Step 4: Commit and Tag

This project uses jj (Jujutsu) in colocated mode with git. Create a release commit and tag:

# Describe current change as release commit
jj describe -m "chore(release): v<new_version>"

# Create new empty change for future work
jj new

# Get the git commit id of the release commit (jj's @- syntax doesn't work with git)
jj log -r @- -T 'commit_id' --no-graph

# Create tag using the git commit id
git tag v<new_version> <commit_id>

Step 5: Push Changes

Push the commit and tag to remote:

# Move main bookmark to the release commit, then push
jj bookmark set main -r @-
jj git push

# Push the tag
git push origin v<new_version>

Step 6: Build and Publish

Build and publish to PyPI:

uv build
uv publish

Error Handling

  • If git working directory is dirty, prompt user to commit or stash changes first
  • If UV_PUBLISH_TOKEN is not set, warn user before publishing step
  • If any step fails, provide clear error message and recovery instructions

Scripts

  • scripts/bump_version.py - Handles semantic version bumping
  • scripts/update_changelog.py - Updates CHANGELOG.md with commits since last tag