release

C3 Plugin Release

Arguments

$ARGUMENTS

Current State

• Current version: !cat "$CLAUDE_PROJECT_DIR/.claude-plugin/plugin.json" | grep '"version"' | head -1 | sed 's/.*"version": "\([^"]*\)".*/\1/'
• Last git tag: !cd "$CLAUDE_PROJECT_DIR" && git describe --tags --abbrev=0 2>/dev/null || echo "none"

Instructions

You are preparing a release for the C3 plugin. Follow these steps:

Step 1: Gather Change Information

Run these git commands to understand what changed:

# Get commits since last tag (or all if no tags)
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -n "$LAST_TAG" ]; then
    git log "$LAST_TAG"..HEAD --oneline --no-merges
else
    git log --oneline --no-merges -20
fi

Also check the diff summary:

if [ -n "$LAST_TAG" ]; then
    git diff "$LAST_TAG" --stat | tail -5
fi

Step 2: Determine Version Bump

Analyze the commits using conventional commit prefixes:

Prefix	Bump Type	Examples
feat	minor	New feature, new skill, new command
fix	patch	Bug fix, typo correction
docs	patch	Documentation only
refactor	patch	Code restructure, no behavior change
chore	patch	Maintenance, dependency updates
BREAKING CHANGE or exclamation suffix	major	Breaking changes to skill behavior

Decision rules:

1. If user specified major, minor, or patch in $ARGUMENTS, use that
2. Otherwise, analyze commits and recommend based on:
   • Any feat: commits → minor
   • Any breaking changes → major
   • Only fixes/docs/chores → patch

Step 3: Confirm with User

Use AskUserQuestion to confirm:

• The determined version bump (showing current → new version)
• Summary of changes to include in changelog

Step 4: Validate plugin.json (CRITICAL)

Claude Code uses auto-discovery for plugin components. Explicit path declarations break plugin loading.

Read .claude-plugin/plugin.json and REMOVE these fields if present:

• "commands": "..."
• "skills": "..."
• "agents": "..."
• "hooks": "..."