Release Manager

Attended release gatekeeper: consume shared readiness verdicts, offer confirmed single-service pushes (publish_commit in Pi), track CI failures and rollouts, and recommend watch cadence. Maintenance and restarts are separately owned.

9 starsOther

Install

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

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 Manager

One invocation is one attended tick. Readiness is advisory; a `READY` result is not permission to
push. One immediate explicit answer authorizes one visible command, never a batch or a later tick.
For a passive dashboard use `/release-status`; `/watch-release` schedules this skill unchanged.

## Usage

```text
/release-manager
/release-manager web
```

## Ownership

- `ready-to-release/scripts/release-gates` alone collects, normalizes, and evaluates release gates.
  Do not recompute them, fall back to independent checks, or override a hold with local tests.
- This skill owns the attended push decision, local release decisions/rollout tracking, CI-failure
  tracking, and cadence. It never repairs setup, reconciles manifests, syncs configuration,
  restarts workloads, or flips flags. Missing adapters are a setup handoff, not an automatic fix.
- `/release-maintenance` owns explicitly requested reconciliation, config sync, restart, and
  evidence-backed rollout acknowledgement. Never invoke it from a manager/watch tick, even when
  the user answers a tick question. A maintenance request ends this tick with a handoff instead.
- Run one active manager per project state file. Persist state only through the `release-state`
  helper below, never with Write, an editor or shell redirection. A `conflict` means another writer
  changed the file: read again and redecide from fresh state, never resend the same patch blindly.
Read the full skill on GitHub

Details

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

FAQ

What does the Release Manager skill do?

Attended release gatekeeper: consume shared readiness verdicts, offer confirmed single-service pushes (publish_commit in Pi), track CI failures and rollouts, and recommend watch cadence. Maintenance and restarts are separately owned.

How do I install the Release Manager skill?

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

Is Release Manager popular?

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

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.