Release Readiness Review

Status: Experimental

This proposed skill helps the team make release and deployment decisions consistently, especially when a change touches hosted apps, AWS infrastructure, scheduled jobs, data collection, auth, or other live surfaces.

Purpose

Release work often mixes code readiness, operational safety, and deployment evidence. This skill gives agents a repeatable checklist for turning a branch, PR, or deployment request into a concise go/no-go brief with validation and rollback notes.

When To Use

• "Review this PR for release readiness before we deploy it."
• "Ship this to production and tell me what smoke checks passed."
• "Make a rollback and smoke checklist for this dashboard change."

Requirements

• Access to the relevant repo, branch, PR, runbook, deployment logs, or dashboard URLs.
• Permission to inspect the target environment.
• Explicit approval before production-impacting or externally visible changes.
• No secret values, raw auth headers, or sensitive deployment logs in chat or committed files.

Install

Install only for intentional trial while this skill is Experimental:

scripts/install-skill.sh release-readiness-review copilot /path/to/project-repo
scripts/install-skill.sh release-readiness-review codex
scripts/install-skill.sh release-readiness-review cursor /path/to/project-repo

Typical Output

• Release scope, target environment, and user-impact summary.
• Readiness matrix with blockers or missing evidence.
• Validation and live smoke evidence.
• Rollback path and residual risk.
• Links or IDs for commits, PRs, deployments, invalidations, tickets, or status updates.

Testing

• Dry-run against a small static-site change with a known deploy runbook.
• Dry-run against an infrastructure change that should require explicit production approval.
• Confirm the skill stops instead of deploying when target environment or rollback path is unclear.
• Confirm it redacts or avoids secret-bearing logs.

Example Prompt

Use the release readiness skill to review this branch and tell me whether it is safe to deploy to dev. Include smoke checks and rollback notes.