release-checklist

Reviews changes for release readiness across compatibility, tests, migrations, documentation, and rollback.

154|27|Updated Aug 3, 2026

Search Tags:#code review #checklist #deployment #rollback #compatibility #migration #release

One-click install

npx skills add https://github.com/openvetta/open-vetta --skill release-checklist-openvetta

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/openvetta/open-vetta/tree/main/packages/coding-agent/examples/runtime-agents/skills/reviewer/release-checklist
Command: npx skills add https://github.com/openvetta/open-vetta --skill release-checklist-openvetta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a change without a structured review often leads to broken compatibility, missing migrations, undocumented behavior, or no rollback plan. This Skill provides a consistent release-readiness review so blockers are surfaced before deployment. ## Core Features & Use Cases - Compatibility Review: Checks whether the change breaks existing interfaces, consumers, or supported environments. - Test and Migration Impact: Verifies test coverage and assesses database or data migration consequences. - Documentation and Rollback Audit: Confirms documentation is updated and a rollback strategy exists, then reports every unresolved release blocker. - Use Case: Before merging a pull request that alters an API schema, run this review to confirm tests pass, migration scripts exist, docs are updated, and a rollback path is defined. ## Quick Start Review whether this change is ready to release and report any unresolved blockers.

Frequently Asked Questions about release-checklist

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

FAQPage Schema

How do I check if a change is ready to release?▼

Run a structured release review covering compatibility, test coverage, migration impact, documentation updates, and rollback strategy. This Skill walks through each dimension and reports every unresolved blocker before you ship.

What should a release readiness checklist include?▼

A release readiness checklist should cover backward compatibility, passing tests, database or data migration impact, updated documentation, and a defined rollback strategy. Any unresolved item in these areas is a release blocker.

How to review migration impact before deploying?▼

Assess whether the change alters schemas, data formats, or stored state, and confirm migration scripts and rollback paths exist. This Skill includes migration impact as an explicit review dimension.

When should I not release a change?▼

Hold the release when compatibility is broken, tests are missing or failing, migrations are unplanned, documentation is stale, or no rollback strategy exists. The review reports each unresolved blocker so the decision is explicit.