菜单
Use to cut a new release — bumps the workspace version, commits, tags, and pushes. The tag push triggers the release CI workflow which publishes to crates.io. Wraps scripts/release.sh with a pre-flight checklist so a release doesn't ship broken.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use to verify changes to agents, capabilities, integrations, steps, or runtime end-to-end before declaring a task done. Boots the full server stack with embedded WASM runner and separate DBs, then drives the server HTTP API to create, compile, and execute a workflow and assert observable behavior. Unit tests are not sufficient — agent/runtime changes must e2e-verify.
Use when local dev state has drifted into a weird shape — failing migrations, half-applied schema changes, stale cached binaries, suspended instances clogging the system. Wipes the e2e DBs and data dir and gives you a clean slate. Distinct from e2e-verify which assumes a clean env.
Use to set up the right RUST_LOG filters and tail server + environment logs scoped to a specific tenant, instance, or component. Saves the "what's the right log filter again" lookup. Pair with trace-instance when you need both API state and live log output.
Use when a workflow that uses a connection misbehaves — to see stored params (secrets masked), token state, rate-limit history, and which integration it belongs to. Catches stale OAuth tokens and misconfigured connection params before you blame the agent.
Use to get a quick health view of a workflow — its definition, registered versions, recent instances and their statuses, and which connections it touches. The "is this thing healthy / what does it look like right now" view, distinct from trace-instance which drills into one specific run.
Use for the tight inner loop when developing or debugging a single capability — rebuild only the changed crate, recompile a small test workflow that exercises it, register, run, dump output. ~10s feedback vs full e2e-verify. Use e2e-verify for the final pre-commit check; use this while iterating.
| name | release |
| description | Use to cut a new release — bumps the workspace version, commits, tags, and pushes. The tag push triggers the release CI workflow which publishes to crates.io. Wraps scripts/release.sh with a pre-flight checklist so a release doesn't ship broken. |
The release flow is a single script: scripts/release.sh <patch|minor|major>.
Run before the script. It refuses to run with a dirty tree, but it won't catch logic regressions.
On main, up to date with origin.
git checkout main && git pull --ff-only
Working tree clean.
git status
No staged or unstaged changes. The script will abort otherwise.
CI green on main. Check .github/workflows. If CI is red, fix before tagging — the release workflow runs against the tagged commit.
e2e-verify passes locally. A clean tree doesn't mean the tag will work end-to-end. Run the e2e-verify skill against the commit you're about to tag.
Pick the bump type. Follow semver:
patch — bug fixes, no API changesminor — new features, backwards-compatiblemajor — breaking changes (rare; coordinate with downstream consumers)./scripts/release.sh patch # or minor, or major
The script:
v*.*.* tag, computes the next version.Cargo.toml files.git add -A, commits as Release <version>, tags as v<version>.y to push commit + tag to origin.The tag push triggers .github/workflows/release.yml, which publishes crates.io artifacts. Watch the workflow run — if publish fails partway through (e.g. a sub-crate already published), the recovery is not to delete and re-tag (v<X> is permanent on crates.io). Cut a new patch release with the fix instead.
git tag -d v<version> is safe.git reset --hard HEAD~1 (only if you haven't pushed).Cargo.toml but no commit yet: git checkout -- . to revert.Per repo policy: never force-push a release. If a tagged release is broken, ship a patch on top.
Cargo.toml files with workspace versionsRelease <version>v<version>