db-mcp: Skill for Claude Code

Release Skill

Cut a db-mcp release. Arguments: patch (default), minor, or major.

Step 1 — Determine bump type and compute new version

Parse $ARGUMENTS. If empty or "patch" → patch bump. "minor" → minor bump. "major" → major bump.

Read current version from packages/core/pyproject.toml (project.version field).

Compute the new version by applying the bump:

• patch: X.Y.Z → X.Y.(Z+1)
• minor: X.Y.Z → X.(Y+1).0
• major: X.Y.Z → (X+1).0.0

State the bump type and new version clearly before proceeding.

Step 2 — Ensure we are on main and it is clean

git branch --show-current
git status --short

If not on main, switch to main and pull latest:

git checkout main
git pull origin main

Abort with a clear message if there are uncommitted changes (tracked files only — untracked files are fine). Do NOT stash or discard changes; ask the user to handle them first.

Step 3 — Bump version in two files

Edit packages/core/pyproject.toml: change version = "OLD" → version = "NEW". Edit packages/core/src/db_mcp/__init__.py: change __version__ = "OLD" → __version__ = "NEW".

Step 4 — Write release notes

Create docs/releases/vNEW.md with the required sections:

1. # Release vNEW - {Title} — derive a short title from recent commit messages
2. ## Overview — one-paragraph summary of what changed
3. ## Highlights — bullet list of user-facing changes
4. ## New Features / ## Bug Fixes — as applicable (omit empty sections)
5. ## Files Changed — table of key files and what changed
6. ## Testing — test counts and lint status (get counts by running tests or reading recent output)

To understand what changed since the last release, run:

git log $(git describe --tags --abbrev=0 HEAD^)..HEAD --oneline

Then run:

uv run python scripts/release_notes.py prepare NEW

This validates the release notes structure and prepends them into CHANGELOG.md.

Step 5 — Update uv.lock

uv lock

Step 6 — Validate