conch: Skill for Claude Code

Release New Version & Draft GitHub Release

Bumps the project version across all config files, updates the CHANGELOG, pushes a tag, and creates a draft GitHub release using gh.

When to Use

• Releasing a new patch, minor, or major version of r-shell
• Creating a GitHub draft release with changelog notes
• Tagging a new version and pushing to origin

Procedure

1. Determine Bump Type

Ask (or infer from the argument) whether this is a patch, minor, or major bump:

Type	When	Example
patch	Bug fixes, small tweaks	1.2.3 → 1.2.4
minor	New features, backward-compatible	1.2.3 → 1.3.0
major	Breaking changes	1.2.3 → 2.0.0

2. Run the Version Bump Script

# Replace <type> with patch, minor, or major
pnpm run version:<type>

This updates all version locations atomically and creates a git commit:

• package.json
• cli/Cargo.toml
• cli/Cargo.lock
• CHANGELOG.md (adds a skeleton section)

Read the new version from package.json:

node -p "require('./package.json').version"

3. Update CHANGELOG.md

First, get the actual commits since the previous tag. Find the previous tag and list every commit:

PREV_TAG=$(git tag --sort=-v:refname | sed -n '2p')   # second-newest tag
git log "${PREV_TAG}..HEAD" --oneline --no-merges

⚠️ CRITICAL — Do NOT fabricate changelog entries. Every bullet point MUST correspond to a commit in the output above. Do not copy bullets from older versions, do not invent features, and do not summarize the whole project history.

Open CHANGELOG.md and fill in the new version section that the script created. Replace the placeholder lines with actual release notes derived strictly from the commit list, grouped under:

• ### Added — new features (feat: commits)
• ### Changed — modifications to existing behavior (refactor:, perf: commits)
• ### Fixed — bug fixes (fix: commits)
• ### Removed — anything deleted (omit section if empty)