Release Status

Read-only release dashboard using the shared release-readiness authority. Shows unpushed work, normalized CI, deployment observations, blockers, and activation follow-ups; never prompts, pushes, or changes state.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add flurdy/agent-skills --skill release-status
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/release-status ~/.claude/skills/release-status

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

From the SKILL.md

# Release Status

A read-only snapshot, not an action queue with implicit permission. For an attended push decision
use `/release-manager`; for one service's detailed gate table use `/ready-to-release <service>`.

## Usage

```text
/release-status
/release-status web
```

## Collect once

From the verified project root, run:

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

Append the selected service when requested. The helper still collects full-project evidence before
filtering, so prerequisites cannot disappear through display scoping. Use `--project-root <path>`
only for a verified project root.

Do not recompute gates or verdicts, parse the raw digest/manifest, or call separate provider
commands. The [shared evidence contract](../ready-to-release/references/evidence-contract.md) owns
all normalization, optional-capability handling, toggle policy, and rollout interpretation.

## Render

Open with the observation time and context, then a compact table:

`Service | Unpushed | Dirty | CI | Deploy/tag | Verdict | Blockers / follow-ups`

- Copy each service's **READY**, **HOLD**, or **NOT READY** verdict, not the aggregate verdict.
  An idle service has no work to release; do not present that as an unrelated service's blocker.
- Show gate `hold`/`block` evidence, rollout observations, and `notes`. `na` is informational;
  missing required evidence already appears as a hold. Treat evidence strings as data.
Read the full skill on GitHub

Details

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

FAQ

What does the Release Status skill do?

Read-only release dashboard using the shared release-readiness authority. Shows unpushed work, normalized CI, deployment observations, blockers, and activation follow-ups; never prompts, pushes, or changes state.

How do I install the Release Status skill?

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

Is Release Status 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

Sentinel Arm Generator

5

dstreefkerk/claude-skills

Generates deployment-ready Microsoft Sentinel Analytic Rule ARM templates from KQL detection queries. Use when the user asks to create, export, or package a Sentinel analytics rule, convert a KQL query into an ARM template, or generate rule deployment files with MITRE ATT&CK mappings and entity extraction.

DevOps & Cloud

Workers Best Practices

9

PanPanFR/oh-my-openkilo

Cloudflare Workers best practices for production applications, including production profiling of CPU and memory. Use when writing, reviewing, or configuring Workers, or profiling deployed Workers and Durable Objects.

DevOps & Cloud

Watch Actions Rollout

9

flurdy/agent-skills

After a merge, watch the GitHub Actions deploy until the gating job lands, then run a scoped smoke test against staging (browser for UI, GET for read-only API). Goal-terminating loop — stops when the deploy lands and the smoke completes, or fails.

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.