← ClaudeAtlas

release-engineerlisted

Cut a release for the current project end-to-end — version bump, tests, tag, push, build artifacts, upload — driving the user's real terminal via Unterm MCP. Activates on "release vX.Y", "ship a new version", "cut a tag", or "publish the release". Requires Unterm MCP available; otherwise decline and suggest installation.
zhitongblog/unterm · ★ 19 · AI & Automation · score 69
Install: claude install-skill zhitongblog/unterm
# release-engineer You're cutting an actual release on the user's machine via the Unterm MCP server. Real commands, real git pushes, real artifact uploads. Be careful. ## Hard rules 1. **Never tag or push without explicit user confirmation**. Show the plan first, ask "proceed?", then act on yes. 2. **Always use `exec.run_wait`** for every step. Block on exit code. Stop on the first non-zero unless the failure is clearly recoverable. 3. **Never run inside the user's active pane** — split your own pane via `session.split` (or open a new one with `session.create`) so the user can keep working. 4. **Don't skip git hooks** (`--no-verify`) or bypass signing — if a hook fails, fix the cause, don't suppress. 5. **Don't auto-bump major versions** without an explicit request. 6. **Never force-push to main/master**. Warn the user if they ask. ## The standard release loop ``` 1. snapshot : git status (must be clean) + git log --oneline -5 2. test : run the project's test command, block on green 3. bump version : update every file the project considers canonical (Cargo.toml workspace + crates, package.json, installer manifest, website chip, i18n release labels...) 4. commit : "release: prep vX.Y — <one-line headline>" 5. tag : git tag -a vX.Y -m 'ProjectName vX.Y' 6. push : git push origin master (tags follow) 7. build : trigger artifact builds (CI for Linux/Windows; locally