How do I install the Release Guard skill?

Run npx skillmds@latest add tomevault-io/release-guard in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release Guard safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Guard?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Guard free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Guard?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Guard by tomevault-io — Agent Skill

Name: Release Guard
Author: tomevault-io

Release Guard

STRICT GitHub release gatekeeper. Blocks premature releases (from develop, incomplete CI). Verifies PR merged to main + ALL CI passed before allowing tag/release. Triggers on "release", "tag", "publish", "deploy", "version". Use when this capability is needed.

tomevault-io d6e2199 2 files · 3.3 KB Updated Sep 17, 2026

File contents

Release Guard Skill

Core Rules (NEVER VIOLATE)

Releases ONLY from main after PR merge.
ALL CI jobs must COMPLETE + SUCCESS. NO queued jobs.
Verify branch protection requires status checks.
Version MUST match tag before creating release (cargo-dist requirement).

Activation Steps

PR Check: Ask for PR# if needed. Run gh pr view $PR_NUM --json state,baseRefName. Must: state=CLOSED, baseRefName=main.
Branch: git branch --show-current + gh repo view --json default_branch. Fail if not main.
CI: gh run list --branch main --limit 5 --json status,conclusion. ALL: completed + success. Log/screenshot.
Clean: git status (clean working dir).
Version Check (CRITICAL): grep '^version =' Cargo.toml must match tag (without 'v' prefix).

Fail Response

🚫 BLOCKED: [Exact violation]
Fix:
- Merge PR to main
- Wait CI: gh run list --branch main
- git checkout main && git pull
- BUMP VERSION in Cargo.toml FIRST (must match tag)
Re-run task.

Version Mismatch Example (v0.1.22 Incident)

Tag: v0.1.22 pushed at commit 05c0481
Cargo.toml version: 0.1.21 (MISMATCH!)
Result: cargo-dist failed: "This workspace doesn't have anything for dist to Release!"

Fix: ALWAYS bump version BEFORE pushing tag.
Use: cargo release patch|minor|major (handles atomically)

Pass: Safe Release

Semver check: cargo semver-checks check-release --workspace (ADR-034)
Tag: vMAJOR.MINOR.PATCH (semantic).
Prefer: cargo release patch|minor|major (ADR-034)
Fallback: gh release create v1.2.3 --generate-notes --target main
Confirm before execute.

Examples

User: "Create release from develop PR #199" → BLOCK: Wrong branch.
User: "Tag v1.0.0 after PR #199" → Check PR/CI/branch → Proceed if pass.

Progressive disclosure: For CI details, see ci-reference.md if needed.


## Best Practices Applied
- **Description**: Keyword-rich for matching ("release", "tag").
- **allowed-tools**: Read + Bash wildcards (gh/git CLI). Install `gh`.[2]
- **Structure**: Essential in SKILL.md; link supports (add `ci-reference.md` for details).
- **Load/Test**: Restart Claude Code. Ask "What Skills available?". Test: "Create release PR #199".

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/d-o-hub) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->

---name: release-guarddescription: STRICT GitHub release gatekeeper. Blocks premature releases (from develop, incomplete CI). Verifies PR merged to main + ALL CI passed before allowing tag/release. Triggers on "release", "tag", "publish", "deploy", "version". Use when this capability is needed.---# Release Guard Skill## Core Rules (NEVER VIOLATE)- Releases **ONLY** from **main** after PR merge.- **ALL** CI jobs must COMPLETE + SUCCESS. NO queued jobs.- Verify branch protection requires status checks.- **Version MUST match tag** before creating release (cargo-dist requirement).## Activation Steps1. **PR Check**: Ask for PR# if needed. Run `gh pr view $PR_NUM --json state,baseRefName`. Must: state=CLOSED, baseRefName=main.2. **Branch**: `git branch --show-current` + `gh repo view --json default_branch`. Fail if not main.3. **CI**: `gh run list --branch main --limit 5 --json status,conclusion`. ALL: completed + success. Log/screenshot.4. **Clean**: `git status` (clean working dir).5. **Version Check** (CRITICAL): `grep '^version =' Cargo.toml` must match tag (without 'v' prefix).## Fail Response```🚫 BLOCKED: [Exact violation]Fix:- Merge PR to main- Wait CI: gh run list --branch main- git checkout main && git pull- BUMP VERSION in Cargo.toml FIRST (must match tag)Re-run task.```## Version Mismatch Example (v0.1.22 Incident)```Tag: v0.1.22 pushed at commit 05c0481Cargo.toml version: 0.1.21 (MISMATCH!)Result: cargo-dist failed: "This workspace doesn't have anything for dist to Release!"Fix: ALWAYS bump version BEFORE pushing tag.Use: cargo release patch|minor|major (handles atomically)```## Pass: Safe Release- Semver check: `cargo semver-checks check-release --workspace` (ADR-034)- Tag: vMAJOR.MINOR.PATCH (semantic).- Prefer: `cargo release patch|minor|major` (ADR-034)- Fallback: `gh release create v1.2.3 --generate-notes --target main`- Confirm before execute.## Examples- User: "Create release from develop PR #199" → BLOCK: Wrong branch.- User: "Tag v1.0.0 after PR #199" → Check PR/CI/branch → Proceed if pass.Progressive disclosure: For CI details, see [ci-reference.md](ci-reference.md) if needed.```## Best Practices Applied- **Description**: Keyword-rich for matching ("release", "tag").- **allowed-tools**: Read + Bash wildcards (gh/git CLI). Install `gh`.[2]- **Structure**: Essential in SKILL.md; link supports (add `ci-reference.md` for details).- **Load/Test**: Restart Claude Code. Ask "What Skills available?". Test: "Create release PR #199".---> Converted and distributed by [TomeVault](https://tomevault.io/claim/d-o-hub) — claim your Tome and manage your conversions.

Frequently asked questions