safebreach-mcp: Skill for Claude Code

Create MCP Release

Prepare a release candidate for the SafeBreach MCP servers. Bumps version in pyproject.toml, generates changelog from git history, and creates a GitHub PR.

Step 1: Validate Environment

1. Read pyproject.toml in the repo root — confirm it contains name = "safebreach-mcp-server". If not found, halt: "This command must be run from the safebreach-mcp repository root."
2. Check working tree is clean:

   git status --porcelain
   

   If dirty, present options via AskUserQuestion:
   • "Stash changes" — run git stash push --include-untracked -m "pre-release stash" then continue (the --include-untracked flag is required to capture new/untracked files, not just modified ones)
   • "Abort" — stop the workflow

Step 2: Ask Version Bump Type

Present the choice via AskUserQuestion:

• Minor — increment minor version, reset patch (e.g., 1.1.0 → 1.2.0)
• Major — increment major version, reset minor and patch (e.g., 1.1.0 → 2.0.0)

Step 3: Determine Current Version and Calculate Next

1. Read pyproject.toml and extract the version field from line 3 (format: version = "X.Y.Z")
2. Parse into major, minor, patch integers
3. Apply the bump:
   • Minor: increment minor, set patch to 0
   • Major: increment major, set minor and patch to 0
4. Display: Version: {current} → {next}

Step 4: Create Release Branch

1. Ensure on main with latest:

   git checkout main && git pull origin main
   

2. Construct branch name: release_{next_version} (e.g., release_1.2.0)
3. Check if branch already exists:

   git branch -a --list "*release_{next_version}*"
   

4. If it exists, ask the user via AskUserQuestion:
   • "Use existing branch" — checkout the existing branch
   • "Create with suffix" — use release_{next_version}-v2
   • "Abort" — stop the workflow
5. Create and checkout: git checkout -b {branch_name}

Step 5: Bump Version

Use the Edit tool to update pyproject.toml line 3, changing the old version string to the new one:

version = "{current}" → version = "{next}"