메뉴
Release a new version of Loom — bumps version, runs checks, tags, and pushes
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | release |
| description | Release a new version of Loom — bumps version, runs checks, tags, and pushes |
| argument-hint | <version> |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Edit, Grep, Glob |
Cut a new release of Loom. The version argument must be a valid semver string (e.g. 0.2.0).
Validate version argument. The argument must match ^[0-9]+\.[0-9]+\.[0-9]+$ (no leading v). Abort with a clear error if it doesn't.
Check preconditions. All of these must pass — abort on failure:
main branchgit status --porcelain is empty)v<version> does not already exist (git tag -l v<version>)git pull --ff-only origin mainBump version. Edit the workspace Cargo.toml at the repo root — change version = "..." in [workspace.package] to the new version. This is the single source of truth; crates inherit via version.workspace = true.
Sync lockfile. Run cargo generate-lockfile to update Cargo.lock.
Run checks. All must pass:
cargo fmt --all --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --locked
Commit. Stage Cargo.toml and Cargo.lock, then:
git commit -m "release: v<version>"
Tag.
git tag v<version>
Push.
git push origin main
git push origin v<version>
Wait for the release workflow. Poll until complete:
gh run list --workflow=release.yml --limit=1 --json databaseId,status --jq '.[0]'gh run view <run-id> every 30 seconds until the status is completedsuccess, print a success message with the release URL: https://github.com/acartine/loom/releases/tag/v<version>failure, print the failure details from gh run view <run-id> --log-failed and abortSmoke-test. Print the smoke-test command for the user to run:
curl -fsSL https://raw.githubusercontent.com/acartine/loom/main/install.sh | sh && loom --version
Use the Knots workflow through `kno` when asked to create a new knot from a rough request and you need a concise goal, exact acceptance criteria, and repeatable verification steps.
Use the Knots workflow through `kno` when asked to drive a knot end to end, run a claimed knot to completion, or keep advancing a knot until it reaches a terminal state such as `SHIPPED`, or a passive waiting state such as `BLOCKED` or `DEFERRED`.
Use the Knots workflow through `kno` when asked to orchestrate an execution plan from start to finish, processing waves sequentially, steps within each wave sequentially, and launching knots within each step concurrently.
Use the Knots workflow through `kno` when asked to create a knot, work on a specific knot, claim or execute a knot, advance a knot to its next state, or recover or roll back a knot safely after blocked or failed work.