// Orchestrate a multi-step Atuin CLI release — version bumping, changelog generation, PR creation, tagging, and crates.io publishing. Invoke with /release or /release <version>.
[HINT] 下载包含 SKILL.md 和所有相关文件的完整技能目录
| name | release |
| description | Orchestrate a multi-step Atuin CLI release — version bumping, changelog generation, PR creation, tagging, and crates.io publishing. Invoke with /release or /release <version>. |
| disable-model-invocation | true |
| argument-hint | ["version"] |
You are orchestrating a release of the Atuin CLI. Follow the steps below in order, pausing at each checkpoint for user confirmation. Do not skip steps or combine them.
sed -n '/^\[workspace\.package\]/,/^\[/s/^version = "\(.*\)"/\1/p' Cargo.tomlgit describe --tags --abbrev=0 2>/dev/null || echo "none"git-cliff --bumped-version 2>/dev/null | sed 's/^v//' || echo "(unknown)"Verify these tools are installed: git, gsed, cargo, gh, git-cliff.
Use command -v for each. If any are missing, report which ones and stop.
The target version may be provided as $ARGUMENTS. If it's empty, use
AskUserQuestion to ask for the new version (show the current state above
for reference).
After determining the version:
- (e.g. 18.15.0-beta.1), it is a prerelease.
Note this — it affects changelog and publish behavior later.current → new and whether it's a prerelease.Clone a fresh copy into a temp directory:
WORKDIR=$(mktemp -d)
git clone git@github.com:atuinsh/atuin.git "$WORKDIR"
Print the working directory path so the user can find it if needed.
All subsequent Bash commands run from $WORKDIR.
Create a release branch named after the version (no v prefix):
git checkout -b <VERSION>
Replace the old version with the new one in all Cargo.toml files.
Escape dots in the old version so sed treats them literally:
VERSION_PATTERN="${OLD_VERSION//./\\.}"
find . -type f -name 'Cargo.toml' -not -path './.git/*' \
-exec gsed -i "s/$VERSION_PATTERN/$NEW_VERSION/g" {} \;
Run cargo check to update Cargo.lock.
Show git diff --stat and the version-related lines from the diff:
git diff --unified=0 -- '*.toml' | grep -E '^\+.*version' | grep -v '^\+\+\+'
Verify the workspace version was actually updated by re-reading it
from Cargo.toml.
Checkpoint: Show the diff summary and ask the user to confirm the version changes look correct.
The changelog strategy differs for prereleases vs stable releases:
Prerelease: Maintain a running ## [unreleased] section containing
all changes since the last stable release. Use:
git-cliff --unreleased --strip all
(cliff.toml's ignore_tags already ignores beta/alpha tags, so
--unreleased spans back to the last stable release automatically.)
Stable release: Generate a versioned entry that replaces the
[unreleased] section. Use:
git-cliff --unreleased --tag "v<VERSION>" --strip all
Then update CHANGELOG.md:
If an existing ## [unreleased] or ## [Unreleased] section exists,
remove it entirely (the heading and all content up to the next
## heading).
Insert the new entry before the first existing ## version heading.
Checkpoint: Read and display the new changelog entry to the user. Ask if they want any edits. If so, make the requested changes using the Edit tool. Repeat until they're satisfied.
Stage all changes and commit:
chore(release): prepare for release <VERSION>
Push the branch with --set-upstream origin.
Extract the changelog entry body (everything between the new ## heading
and the next one) for the PR description.
For prereleases, the heading to match is ## [unreleased].
For stable releases, it's ## <VERSION> (escape dots in the awk pattern).
Create the PR:
gh pr create \
--title "chore(release): prepare for release <VERSION>" \
--body "<body with changelog>" \
--repo atuinsh/atuin
Show the PR URL to the user.
Start a persistent Monitor that polls the PR status every 30 seconds. The monitor script must:
MERGED, exit 1 on CLOSEDThe rollup mixes two entry shapes: CheckRun entries use status +
conclusion, while StatusContext entries use state. A check counts
as "passing" when it's in a terminal state with a non-failing outcome.
Treat SUCCESS, SKIPPED, and NEUTRAL as passing — some release
workflows (e.g. announce, build-global-artifacts) are conditional
and report SKIPPED on non-tag events, which is expected, not a
failure.
Example monitor script (substitute the actual PR number):
checks_passed=false
while true; do
json=$(gh pr view PR_NUM --repo atuinsh/atuin --json state,statusCheckRollup 2>/dev/null) || { sleep 30; continue; }
state=$(echo "$json" | jq -r '.state')
case "$state" in
MERGED) echo "PR #PR_NUM has been merged!"; exit 0 ;;
CLOSED) echo "PR #PR_NUM was closed without merging."; exit 1 ;;
esac
# Only notify once when all checks reach a terminal passing state.
# CheckRun entries carry `status`/`conclusion`; StatusContext entries
# carry `state`. SKIPPED and NEUTRAL count as passing.
if [ "$checks_passed" = false ]; then
counts=$(echo "$json" | jq -r '
[.statusCheckRollup[]?] as $all
| ($all | map(select(
(.status == "COMPLETED" and (.conclusion | IN("SUCCESS","SKIPPED","NEUTRAL")))
or .state == "SUCCESS"
)) | length) as $passing
| ($all | map(select(
(.status == "COMPLETED" and (.conclusion | IN("FAILURE","TIMED_OUT","CANCELLED","ACTION_REQUIRED","STALE")))
or (.state | IN("FAILURE","ERROR"))
)) | length) as $failing
| "\($all | length) \($passing) \($failing)"
' 2>/dev/null)
read -r total passing failing <<<"$counts"
if [ "${failing:-0}" -gt 0 ] 2>/dev/null; then
echo "PR #PR_NUM has $failing failing check(s) — investigate before merging."
checks_passed=true # don't re-notify
elif [ "${total:-0}" -gt 0 ] 2>/dev/null && [ "$total" = "$passing" ]; then
echo "All $total checks passed on PR #PR_NUM — ready to merge!"
checks_passed=true
fi
fi
sleep 30
done
Tell the user to go review and merge the PR. While the monitor runs, you can respond to other questions — the monitor notifications will arrive asynchronously.
When the monitor reports MERGED, proceed to the next step.
If it reports CLOSED, inform the user and stop the release.
Back in the working directory:
git checkout main
git pull
git tag "v<VERSION>"
git push --tags
Tell the user the tag was pushed and the release CI workflow has been triggered.
If this is a prerelease, skip this step entirely and tell the user.
If this is a stable release, ask the user whether to publish.
If yes, publish each crate in dependency order using --no-verify
(the code already passed CI, and verification fails when crates.io
hasn't indexed a freshly-published dependency yet):
atuin-common, atuin-client, atuin-ai, atuin-dotfiles, atuin-history,
atuin-nucleo/matcher, atuin-nucleo, atuin-daemon, atuin-kv,
atuin-scripts, atuin-server-database, atuin-server-postgres,
atuin-server-sqlite, atuin-server, atuin-hex, atuin
For each crate, run from crates/<name>:
cargo publish --no-verify 2>&1
If it fails with "already uploaded", report it as a skip (not an error) —
some crates like atuin-nucleo are versioned independently and may
already be published at their current version.
If it fails for any other reason, stop and report the error.
Summarize what was done:
rm -rf)