release-readiness-reviewer

Evaluate release readiness by verifying CI, artifact, migration, and rollback evidence.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill release-readiness-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-readiness-reviewer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/release-readiness-reviewer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill release-readiness-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns a release readiness check into an evidence-based go/no-go decision, so shipping choices are grounded in verified artifacts instead of assumptions or optimism.

Core Features & Use Cases

  • Release scope validation: Pins the exact release commit, artifact, and included changes before any verdict is made.
  • Evidence-based gating: Verifies CI results, artifact provenance, test signal relevance, migrations, rollback readiness, flags, docs, observability, and approvals.
  • No-Go handling: Treats unknown or missing blocking evidence as a stop condition and records the exact evidence needed to flip the decision.
  • Use case: A deployment candidate has green checks on the branch but a schema migration and new feature flags; this Skill determines whether the specific shipping SHA is truly ready.

Quick Start

Ask for a release readiness review of the exact shipping commit or version and provide the CI, migration, rollback, flag, observability, and approval evidence for that scope.

Frequently Asked Questions about release-readiness-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify release readiness for a production deploy with feature flags and schema migrations?

Release readiness verification evaluates the exact shipping commit by checking CI run links, artifact provenance, migration review, rollback runbook evidence, flag defaults, observability coverage, and change-class approvals to produce a go/no-go verdict.

What evidence is required for a go/no-go deployment decision?

A go/no-go deployment decision requires verifiable CI run links, artifact provenance, test signal relevance, migration review, rollback readiness, feature flag defaults, documentation, observability coverage, and change-class approvals for the specific shipping SHA.

How do I check if a specific artifact and commit is ready to ship?

To check if an artifact is ready to ship, pin the exact release commit and validate CI results, artifact provenance, migration status, rollback readiness, flag defaults, docs, observability, and approvals for that scope.

What happens if rollback runbook evidence or observability coverage is missing during a release review?

If rollback runbook evidence or observability coverage is missing, the release review treats it as a stop condition and records the exact evidence needed to flip the decision from no-go to go.

Can I use a release readiness review for risky migrations and feature-flagged changes?

Yes, release readiness reviews apply to production deploys, merges, risky migrations, feature-flagged changes, and closeout verification where every readiness dimension must be proven with verifiable evidence.

Does a green CI branch guarantee a production go decision?

A green CI branch does not guarantee a production go decision because the review also verifies artifact provenance, migration review, rollback runbook evidence, flag defaults, documentation, observability coverage, and change-class approvals.