agentleFS
Sign inStart free
nledfordnledford/engineering-review-board/skills/release-readiness/SKILL.md

release-readiness

Skill11 starsChanged 11 days agoMITView on GitHub

Assess merge and release readiness across tests, docs, migrations, rollout, rollback, operations, and cross-functional risk. Use for a final ship or hold decision; do not use to choose a semantic patch, minor, or major version, or as the primary implementation, code-review, or deployment workflow.

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dependency-cve-sweep, fleet-standard-adoption and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • berntpoppSkill

    dependency-cve-sweep

    Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.

    Also in 12 projects that use this

  • berntpoppSkill

    fleet-standard-adoption

    Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.

    Also in 12 projects that use this

  • IgorGanapolskySkill

    ci-failure-triage

    Triage a CI / PR check failure by READING the failure body before forming any hypothesis. Triggered whenever a required check is red, a PR is BLOCKED, a merge won't land, or you're about to call a failure "transient", "flaky", "stale", or "orphaned". Prevents dismissing a real failure (e.g. real CodeQL security alerts) as noise.

    Also in 14 projects that use this

  • VersoXBTSkill

    code-quality-review

    Perform structured code reviews enforcing quality standards, naming conventions, architecture patterns, and team agreements. Use when the user says 'review this code', 'code review', 'check quality', 'review my PR', 'what's wrong with this', 'improve this code', 'review before merge', 'peer review', or 'audit this'. Also triggers on 'code quality', 'review standards', 'enforce conventions', 'tech debt check', 'lint review', or when user completes a significant code change.

    Also in 12 projects that use this

  • ffsshhttiikkSkill

    unit-testing

    Unit testing best practices and patterns

    Also in 3 projects that use this

  • jarosser06Skill

    test-strategy

    Plans pytest test strategies for Drift's 90%+ coverage requirement using coverage analysis, edge case identification, and test suite design. Use when determining what tests to write, analyzing coverage gaps, or planning test strategies.

    Also in 4 projects that use this

  • +2 more from berntpopp

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill after implementation and focused reviews are substantially complete, when the remaining question is whether the change is …

    line 8
  2. Very specific:

    Do not use it to replace implementation, a first code review, or a repository's deployment runbook.

    line 17
  3. Distinctive:

    Verify test, build, documentation, configuration, migration, compatibility, and release-note evidence.

    line 31
  4. Distinctive:

    Check rollout, rollback, data recovery, observability, support, and operator readiness.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 47 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

Release Readiness Skill

Use this skill after implementation and focused reviews are substantially complete, when the remaining question is whether the change is safe to merge or release. Load the relevant review skill when security, performance, accessibility, data, or architecture evidence is incomplete.

Apply review-verification-protocol to every blocker, risk finding, and ship-or-hold rationale.

Do not use it to replace implementation, a first code review, or a repository's deployment runbook. Use semantic-versioning to classify the release delta and choose or apply a patch, minor, major, or prerelease version; use ci-release-engineering to create or change checked-in CI and release automation, and container-engineering for Docker/OCI or Compose implementation.

Workflow

  1. Confirm scope, acceptance criteria, dependency changes, and the exact release unit under review.
  2. Verify test, build, documentation, configuration, migration, compatibility, and release-note evidence.
  3. Check rollout, rollback, data recovery, observability, support, and operator readiness.
  4. Confirm that security, performance, accessibility, architecture, and domain risks have either been reviewed or explicitly accepted by the right owner.
  5. Record skipped checks, assumptions, blockers, follow-ups, and residual risk. Decide: Ship, Ship With Follow-ups, Hold for Fixes, or Do Not Ship.

Output

Return the decision, evidence, blockers, follow-ups, rollback considerations, skipped validation, residual risk, and a final release checklist.

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.

Check your setup, free