codemie-code: Skill for Claude Code

CodeMie Release

Automate the release process for CodeMie CLI following semantic versioning and conventional commits.

Pre-flight Checks

Before starting, verify:

1. Branch: Must be on main. If not, stop and ask user to switch.
2. Working directory: Check for uncommitted changes. Warn if present.
3. Current state: Determine what's already done:

   # Current version
   grep '"version"' package.json | sed 's/.*"version": "\(.*\)".*/\1/'
   
   # Latest tag
   git describe --tags --abbrev=0 2>/dev/null
   
   # Check if tag exists
   git tag -l "v<VERSION>"
   
   # Check if release exists
   gh release view "v<VERSION>" 2>/dev/null
   

Analyze Commits and Determine Version

CRITICAL: Always analyze commits to determine the appropriate version bump based on conventional commit types.

1. Get Commit Delta

# Get commits since last release (excluding version bump commits)
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
git log --pretty=format:"%s" ${LAST_TAG:+$LAST_TAG..HEAD} | grep -v "^chore: bump version"

2. Analyze Commit Types

Parse each commit message to identify type:

Conventional Commit Format: <type>(<scope>): <subject>

• Types: feat, fix, docs, style, refactor, perf, test, chore, ci, revert
• Scopes (optional): cli, agents, providers, assistants, config, proxy, workflows, ci, analytics, utils, deps, tests, skills

Breaking Changes: Check commit bodies for BREAKING CHANGE: footer

# Check for breaking changes
git log --pretty=format:"%B" ${LAST_TAG:+$LAST_TAG..HEAD} | grep -q "BREAKING CHANGE:"

3. Determine Version Bump

Version bump rules (highest precedence wins):

1. MAJOR bump (x.0.0) - If any commit contains BREAKING CHANGE: in body
2. MINOR bump (0.x.0) - If any commit has feat: or feat(scope):
3. PATCH bump (0.0.x) - If only fix:, refactor:, perf:, docs:, style:, test:, chore:, ci:, revert: