with one click
release
Version bump and release checklist for remote-store
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.
Menu
Version bump and release checklist for remote-store
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.
Multi-agent orchestration — delegates to domain experts for complex tasks
Triage and act on the weekly drift-guard rolling issue (transitive dependency drift)
Triage and act on the weekly [mutation] rolling issue (mutation-testing run health)
Read review comments from a PR, fix each issue, resolve threads, validate
Create a pull request for the current branch
Post inline review comments on a GitHub PR. Find real issues only.
Based on SOC occupation classification
| name | release |
| description | Version bump and release checklist for remote-store |
| disable-model-invocation | true |
| argument-hint | [patch|minor|major] |
Authority: CONTRIBUTING.md § Release is the authoritative checklist for all phases.
This skill carries the agent-specific execution layer (Phase 4 roles, release template) and
surfaced process notes that an agent must not miss.
Bump level: $ARGUMENTS (ask if missing). Minor = new API/feature/backend, patch = bugfix/refactor, no bump = CI/docs only.
Execute CONTRIBUTING.md § Release (Phases 0–5). Agent notes per phase:
Phase 1 — Update FEATURES.md content only; do NOT touch the version header
(# Features — remote-store vX.Y.Z where X.Y.Z is the current version) —
bump-my-version updates it in Phase 2.
Phase 1 (CHANGELOG completeness cross-check) — Resolve the checklist's
previous_tag_name (vPREV) with gh release view --json tagName --jq .tagName.
See the checklist item for what the gate compares and why its output is discarded.
Phase 2 — bump-my-version reads its target files from [[tool.bumpversion.files]]
in pyproject.toml.
Phase 5 — Agent assists with conda steps (sha256 fetch, recipe update, branch+PR). Staged-recipes steps apply only while conda-forge/staged-recipes PR #32401 is open; once a feedstock exists, only the bot-PR verification step remains.
Title: vX.Y.Z
Description:
## What's Changed
<Extract sections from [Unreleased] in CHANGELOG.md and condense by section,
following the section order in sdd/CLAUDE-REFERENCE.md § Ripple-check table > Detailed checklist.
For each section with content, use brief bullet points (1 line per item, bold topic prefix).
Prefer `**Topic**: explanation` or `**Topic** explanation.` over `**Topic** — explanation`.
Em dashes belong to true asides, not bullet separators (CLAUDE.md § Response style).>
**Links:**
- [Full Changelog](https://github.com/haalfi/remote-store/blob/master/CHANGELOG.md#xyz---yyyy-mm-dd)
- [Compare vPREV...vX.Y.Z](https://github.com/haalfi/remote-store/compare/vPREV...vX.Y.Z)