Library > operate > Release Readiness

Release Readiness

Check changelogs, risks, and rollback steps before you ship.

Overview

An evidence checklist for deciding whether a specific revision is ready to release. Verify the actual candidate, protect concurrent work, and identify missing recovery steps. A positive report never authorizes deployment by itself.

Referenced source

Google SRERelease engineering
Install preview
npx reporadars add release-readiness

CLI coming soon — preview only.

Download draft
Status

Draft. Independent runtime review pending.

Source

Reference linked; draft instructions are original.

Version

0.1.0, pinned in this draft.

Scope

Explicit permissions and limits below.

Agents

Claude Code, Codex, Cursor

Permissions

Read release evidence and run approved local checks. No push, deployment, or migration.

Capabilities

  • Identify the exact release revision and changed scope
  • Check the canonical verification result
  • Review migration and compatibility hazards
  • Require an identifiable rollback artifact
  • Confirm operational ownership and rollout criteria
  • Separate passed checks from missing evidence

How it works

  1. Record revision, worktree state, and scope.
  2. Run or inspect the canonical checks against that revision.
  3. Review rollout and rollback evidence for the changed components.
  4. Return go/no-go findings without activating the release.

This is an original Reporadars draft, informed by the linked source. Compatibility has not been independently runtime-tested; inspect the instructions, permissions, and placement for your agent before use.

Context

Sample editorial notes that frame this draft; they are not release records.

Keep exploring

Drafts in the same category appear first, followed by other catalog samples.