Menu
Use when preparing, validating, tagging, or troubleshooting a RARA release. Enforces the release order that prevents tag versions from diverging from the Cargo package version.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when you need to understand the RARA codebase structure — what each file does, where subsystems live, and how they connect. The index maps every source file to its role.
Handle unused code warnings by investigating purpose via journals, then choose the right fix: suppress, wire-up, or remove.
Add or update tests for the RARA codebase. Use when implementing non-trivial behavior changes, fixing regressions, tightening TUI rendering, or adding repo-specific test coverage in Rust. Especially relevant for focused unit tests, TUI snapshot tests, agent/runtime regressions, and behavior-driven test updates in this repository.
Use when preparing commit messages, pull request titles, or first-line summaries for the RARA repository. Enforces the repo's short conventional title subset using feat, fix, chore, or test.
Use when creating, updating, or reviewing RARA implementation journals under docs/journal/. Applies to dated rollout notes, implementation checkpoints, validation evidence, and deciding what belongs in a journal versus a feature spec or docs/todo.md.
Use when creating, revising, or reviewing RARA canonical feature specs under docs/features/. Applies to stable runtime, TUI, protocol, memory, provider, skill, plugin, and tool contracts, including scope boundaries and validation matrices.
| name | release-rara |
| description | Use when preparing, validating, tagging, or troubleshooting a RARA release. Enforces the release order that prevents tag versions from diverging from the Cargo package version. |
Use this skill for every RARA release request, including version bumps, release-candidate checks, tag creation, workflow dispatch, and release failure triage.
Never create, push, or dispatch a release tag until the Cargo package version matches the target tag version.
For tag vX.Y.Z, [workspace.package].version in Cargo.toml must be
X.Y.Z. For prerelease tag vX.Y.Z-alpha.N or vX.Y.Z-beta.N, the Cargo
version must be X.Y.Z-alpha.N or X.Y.Z-beta.N.
If the release workflow reports:
Tag version X.Y.Z does not match Cargo package version A.B.C.
stop the release. Do not rerun the release workflow until a normal commit bumps
the Cargo version to X.Y.Z and that commit is the one being tagged.
vX.Y.Z, vX.Y.Z-alpha.N, or vX.Y.Z-beta.N.v.main.
main before preparing the version bump.[workspace.package].version in Cargo.toml.Cargo.lock by running cargo metadata --locked first to detect
whether the lock is already consistent; if it is stale, run a normal Cargo
command that refreshes the lockfile.rara package by name, not the first metadata package.chore: bump version to X.Y.ZRun this before creating or pushing a release tag:
VERSION=X.Y.Z
export VERSION
cargo metadata --no-deps --format-version 1 \
| python3 -c 'import json,os,sys; data=json.load(sys.stdin); pkg=next(p for p in data["packages"] if p["name"]=="rara"); actual=pkg["version"]; expected=os.environ["VERSION"]; print(f"rara package version: {actual} (expected {expected})"); sys.exit(0 if actual == expected else 1)'
If this exits non-zero, fix Cargo.toml before continuing.
Only after the required version check passes:
TAG=vX.Y.Z
git tag -a "${TAG}" -m "Release ${TAG}"
git push origin "${TAG}"
For a manual workflow dispatch, the tag must already exist and point to the commit with the matching Cargo version.
If a tag already exists on the wrong commit:
main.Prefer a new patch tag when the bad tag may already have been observed by GitHub Actions, package consumers, or release automation.