cut-release

# Cut a Release — `claude-code-trace` Turns "we should release this" into a tagged, pushed, pipeline-triggered, **publicly published** release with a curated CHANGELOG, in a way that survives the project's strict pre-commit hook chain and stays honest about what's actually shipping. The skill is project-local because the steps depend on this repo's specific shape (three version files, two lockfiles, GH Actions release on `v*` tag, the spec-drift + test-reflection pre-commit hook pair). ## Operating mode The skill is **fully automated end-to-end** and **fully synchronous**. It never calls `AskUserQuestion`, never waits for "yes", never branches on user preference, and **never runs any command in the background**. Every Bash invocation runs in the foreground so the session holds continuously from Phase 1 through Phase 9 — no `run_in_background: true`, no trailing `&`, no `nohup`, no `disown`. This includes long-running steps like `gh run watch` in Phase 7; set the Bash `timeout` parameter to match the expected duration (e.g. 1800000 ms for the release pipeline) rather than detaching. Defaults are deterministic: - **Scope** — always linear: every commit since `git describe --tags --abbrev=0` ships. - **Bump tier** — highest conventional-commit tier in the subset (see `${CLAUDE_SKILL_DIR}/references/conventional-commits.md`). `BREAKING CHANGE:` or `!:` produces a **minor** bump while the version is `0.X.Y` (pre-1.0 caveat) and a **major** bump otherwise; the skill nev...