agentleFS
imtiazrayhanimtiazrayhan/agentscamp-library/skills/release-readiness-reviewer/SKILL.md

release-readiness-reviewer

Skill1 starsChanged 6 days agoMITView on GitHub

Review whether a specific release is ready to ship by checking scope, tests, compatibility, migrations, configuration, observability, rollout, rollback, support, security, and ownership against explicit evidence. Use before a production deployment, major version, risky feature launch, migration, or go/no-go meeting.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check compatibility: Verify API, schema, event, SDK, client, runtime, and infrastructure compatibility across mixed versions and deploy …

    line 14
  2. Distinctive:

    Review rollout and recovery: Check stages, cohorts, bake times, promotion gates, abort thresholds, rollback mechanism, data compatibility, …

    line 18

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Judge one release from current evidence and name what remains unresolved.

Workflow

  1. Establish release identity. Record artifact or commit, environment, intended time, included changes, excluded work, owners, risk class, and user impact. Reject a moving or ambiguous scope.
  2. Review change evidence. Inspect diffs, tests, dependency and configuration changes, generated artifacts, feature flags, operational tasks, and known issues. Link every readiness claim to a source.
  3. Check compatibility. Verify API, schema, event, SDK, client, runtime, and infrastructure compatibility across mixed versions and deploy order. Identify mandatory coordination.
  4. Assess data and configuration. Review migrations, backfills, secrets, environment variables, defaults, capacity, region differences, and one-way transformations. Confirm target values without exposing credentials.
  5. Evaluate verification. Require relevant automated and manual results, unresolved failures, representative environments, performance or load evidence where risk warrants, and post-deploy smoke tests.
  6. Confirm observability and support. Name dashboards, alerts, logs, traces, business signals, on-call owner, escalation, status communication, customer support notes, and known symptom recognition.
  7. Review rollout and recovery. Check stages, cohorts, bake times, promotion gates, abort thresholds, rollback mechanism, data compatibility, recovery time, and fallback when rollback is impossible.
  8. Issue the decision. Choose go, conditional go, or no-go. List blockers separately from accepted risks, conditions, owners, deadlines, approval authority, and evidence that will close each item.

[!WARNING] Do not turn unknowns into implicit acceptance. An unverified migration, missing owner, or untested rollback remains visible in the decision.

Output

Return release identity, risk summary, evidence matrix, blockers, accepted risks, rollout and rollback readiness, observability and support readiness, decision, approvers, and time-bounded conditions. Include the exact post-deploy verification and abort signals.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.