agentsclimarketplace
Sign in

Release readiness

Skill nledford/engineering-review-board/skills/release-readiness

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.From its SKILL.md

Install
npx -y skills add nledford/engineering-review-board --skill release-readiness

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 368 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.