Ready to Release

Read-only release-readiness authority for one service. Collects normalized Git, CI, contract, ordering, toggle, and deployment evidence through one shared evaluator; renders its gate table and verdict without prompting or changing state.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add flurdy/agent-skills --skill ready-to-release
Manual install
git clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/ready-to-release ~/.claude/skills/ready-to-release

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Ready to Release

Answer **is `<service>` ready to push now?** without taking action. A green upstream pipeline
is not proof that unpushed candidate commits have passed remote CI.

## Usage

```text
/ready-to-release web
```

Require a service argument; otherwise print usage and stop without running commands.

## Shared authority

From the verified project root, run:

```bash
~/.agents/skills/ready-to-release/scripts/release-gates web
```

The helper always collects the **full-project** snapshot before selecting the displayed service.
It alone normalizes evidence and computes gates, prerequisites, rollout observations, and verdicts.
`--project-root <path>` selects a different verified project root without changing directories.
Do not recompute a verdict, interpret provider output, transcribe raw evidence into JSON, or
fall back to independent Git/CI/deployment commands. No local-test override for unavailable CI.

[Evidence contract](references/evidence-contract.md) defines adapters, supported policy syntax,
missing-evidence behavior, and fixture evaluation. This contract also serves `/release-status` and
`/release-manager`. Missing project adapters are a setup handoff, never an instruction to repair
symlinks during a readiness check.

## Output

Render the returned service's `gates` as one table: `Gate | Result | Evidence`.
Map `pass` → `✅ pass`, `hold` → `⏳ hold`, `block` → `❌ block`, `na` → `➖ N/A`.
Read the full skill on GitHub

Details

Skill name
ready-to-release
Path
skills/ready-to-release/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Ready to Release skill do?

Read-only release-readiness authority for one service. Collects normalized Git, CI, contract, ordering, toggle, and deployment evidence through one shared evaluator; renders its gate table and verdict without prompting or changing state.

How do I install the Ready to Release skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill ready-to-release. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ready to Release popular?

It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.

Related skills

Architect

9

flurdy/agent-skills

Architecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.

Software Development

Artifact Hygiene

9

flurdy/agent-skills

Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.

Git & Code Review

Backlog Groom

9

flurdy/agent-skills

Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.

Other

Rebase

9

flurdy/agent-skills

Rebase feature or stacked branches, or explicitly integrate a fetched upstream into local main/master. Separate trunk mode proves local replay scope and never enters force-push or PR flows; its mutations require fresh confirmation.

Git & Code Review

Ready to Merge

9

flurdy/agent-skills

Pre-merge gate — verify a PR is green, approved, in sync, and free of obvious risk, then (on explicit approval) squash-merge it. Composes /pr-status, /contract-check, and /review-pr rather than reimplementing them.

Git & Code Review

Reply Comments

9

flurdy/agent-skills

Safely publish prepared PR-feedback outcomes through separately confirmed push, reply, and inline-thread resolution gates. Re-fetches normalized identities before every mutation and keeps retries idempotent.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.