package-release

/package-release

Bumps the npm package version and opens a release PR for claude-second-brain. Does not publish to npm directly — publishing happens automatically via GitHub Actions after the PR is merged.

This skill only touches package.json. If you also want the docs ship log updated in the same PR, run /release instead — it orchestrates /update-docs and this skill together.

When to use

• You've already synced docs (or don't need to) and just want to cut a version.
• The current branch must have commits relative to main.
• For the full combined flow (docs + version), prefer /release.

Argument

Pass a version bump type to skip the confirmation prompt:

Argument	Effect
(none)	Analyze changes and suggest a bump; ask user to confirm
patch	Bump patch version (e.g. 0.1.0 → 0.1.1)
minor	Bump minor version (e.g. 0.1.0 → 0.2.0)
major	Bump major version (e.g. 0.1.0 → 1.0.0)
0.3.0	Use this exact version

Steps

Run each step in order. Stop and report if any step fails.

Step 1 — Capture current state

Run these commands to understand what's changed:

# Current branch
git branch --show-current

# Commits on this branch not yet in main
git log main..HEAD --oneline

# File-level diff summary vs main
git diff main...HEAD --stat

# Current version
cat package.json | grep '"version"'

Record: the branch name, current version, list of commits, and all files changed.

Step 2 — Summarize changes

Categorize all changes from Step 1 into this format:

## Changes in this release

**New features:**
- (e.g. new skill added, new CLI flag, new template file)

**Bug fixes:**
- (e.g. correctness fix in bin/create.ts, template fix)

**Refactors / cleanup:**
- (e.g. code reorganization, no behavior change)

**Docs:**
- (e.g. README updates, CLAUDE.md edits)

Show this changelog to the user. Skip empty categories.

Step 3 — Determine version bump

Read the current version from package.json. Apply semver logic to suggest the next version: