Menu
Bump the project version with a semver rubric, promote the Unreleased changelog section, and verify before committing. Use when the user asks to cut a release, bump the version, or tag a new version.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run ProjectTwelve Unity batch validation and EditMode/PlayMode test suites via Unity 6000.5.1f1. Use when the user or ticket asks to run Unity tests, EditMode fixtures, batchmode validation, or verify test results from TestResults/*.xml.
Log agent sessions, consolidate project memory (dream), promote reviewed memory, and load context for new chats. Use when ending a session, improving cross-session recall, or when the user mentions agent memory, dream, log-session, or memory.md.
Wiki tickets under docs/wiki/tickets/ are the canonical task queue, each linked to a GitHub issue. Use when picking work, claiming an issue, or preparing PR references.
Recommend the next open wiki ticket to work on, ranked by phase then priority, without claiming or mutating anything. Use when the user asks "what's next", to pick the next task, or to start work without a specific ticket in hand.
Sync project-twelve with the Assets/_Licensed submodule via fetch_remotes.py, git hooks, and /fetch-remotes. Use at session start, before picking backlog work, or when the user asks to sync repos or get latest.
Use when the user asks to commit and push, publish, ship, or prepare a release commit. Guides staging only intended changes, writing a Conventional Commit, committing, and pushing to origin after verifying status and diff.
| name | release-bump |
| description | Bump the project version with a semver rubric, promote the Unreleased changelog section, and verify before committing. Use when the user asks to cut a release, bump the version, or tag a new version. |
Repeatable release procedure: decide the semver level, update the version and changelog, verify, and prepare (not push) the release commit.
Find where the version lives, in this order:
VERSION file or CHANGELOG.md (Keep a Changelog) — preferred when presenttools/tile-viz/package.json or tools/world-viz/package.json (offline tooling only)pyproject.toml / setup.cfg (Python), if added laterProjectTwelve note: There is no root CHANGELOG.md or VERSION file yet. For game releases,
Unity uses ProjectSettings/ProjectSettings.asset (bundle version) — that is a human Editor workflow,
not an agent semver bump. If no semver source exists, ask the user whether to:
VERSION + CHANGELOG.md at repo root for agent-infra / tooling releases, ortile-viz@x.y.z), orDo not invent a version file without explicit approval.
Review changes since the last release (git log <last-tag>..HEAD and the Unreleased section of
CHANGELOG.md when it exists):
State the chosen level and the one or two changes that justify it.
CHANGELOG.md exists: rename ## [Unreleased] to ## [X.Y.Z] — YYYY-MM-DD,
keeping its subsections, and add a fresh empty ## [Unreleased] above it.Run checks from AGENTS.md for the changed areas:
python scripts/sync_assistant_trees.py --check
python3 scripts/check_markdown_links.py
python3 scripts/check_paid_assets.py --staged
# Unity / offline tests as applicable — see AGENTS.md test vocabulary
Do not proceed with failing checks.
Suggest a Conventional Commit (chore(release): vX.Y.Z) and the matching annotated tag
(git tag -a vX.Y.Z). Do not commit, tag, or push without an explicit request.