releaselisted

# Release Ships completed work. The skill detects context and runs the right phase: - **On a feature branch with committed work** → WRAP UP phase - **On main after a merge** → CUT RELEASE phase For all message formatting, follow the `conventions` skill. --- ## Step 0 — Auth & Identity (always) Check for a GitHub MCP server in available tools. If none: ```bash gh auth status ``` Stop if neither is available: *"I need the GitHub MCP server or `gh` CLI authenticated. Run `gh auth login`."* Confirm identity — use `mcp__github__get_me` if the GitHub MCP server is available, otherwise: ```bash gh api user --jq '"@\(.login) — \(.name)"' ``` Show the result and ask: *"I'll be acting as @username — is that right?"* Wait for confirmation. --- ## WRAP UP Phase Triggered when on any non-main branch (`feature/`, `fix/`, `chore/`, `refactor/`, `test/`, etc.) with a clean working tree. ### Step 1 — Verify State ```bash git branch --show-current # must not be main git status --porcelain # must be empty — all work committed ``` If the tree is dirty, stop: *"You have uncommitted changes. Commit or stash them first."* ### Step 2 — Detect What Changed ```bash git diff main...HEAD --name-only ``` Determine: - Was a **new skill added**? Look for a new directory under `skills/` not present on main. - Was an **existing skill modified**? Look for changes inside `skills/<name>/`. - Is this a **bug fix, refactor, or docs change**? Look at changed files outside `skills/`. Deri