eforge-release

# /eforge-release Release a new version of eforge. Parses the release type from arguments, checks git status, optionally commits staged changes, generates release notes from the git log, updates CHANGELOG.md, bumps the version on a release PR, tags merged main, pushes the tag, and creates a GitHub Release. ## Workflow ### Step 1: Parse Release Type Read `$ARGUMENTS` to determine the release type: - `--patch` or empty/unrecognized - **patch** (default) - `--minor` - **minor** - `--major` - **major** Store the resolved bump type (one of `patch`, `minor`, `major`) for use in later steps. ### Step 2: Check Git Status Run `git status --porcelain` to determine the repo state. Three possible outcomes: 1. **Clean** (no output) - proceed to Step 4 2. **All changes staged** (all lines start with `M `, `A `, `D `, `R ` - no `?? ` or ` M` or ` D` lines) - proceed to Step 3 3. **Unstaged or untracked changes exist** (any `??`, ` M`, ` D`, or `MM` lines) - **STOP**. Tell the user there are unstaged/untracked changes and they need to stage or stash them first. List the problematic files. ### Step 3: Commit Staged Changes Use the `/git:commit-message-policy` skill to create a commit for the staged changes. Follow the standard commit workflow: 1. Run `git diff --cached` to see what's staged 2. Run `git log --oneline -5` for recent commit style 3. Draft a commit message following Conventional Commits format 4. Create the commit ### Step 4: Generate Release Notes Generate release...