Verified:GitHub

wa:deploy-review

Enforce deploy readiness gates for dev-to-main promotion with a DEPLOY-REVIEW.md verdict.

Updated Mar 26, 2026

Search Tags:#deployment gate #release readiness #dev-to-main #tracker status #CI checklist #GitHub PR merge #changelog verification

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-deploy-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:deploy-review
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/deploy-review
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-deploy-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents faulty or incomplete changes from being promoted from dev to main by enforcing a deploy readiness checklist and producing an auditable verdict report.

Core Features & Use Cases

Promotion readiness gating: Verifies merge-to-dev, validate review outcome, release tag presence, changelog update, and tracker issue closure.
Rigor-based enforcement: Applies Lite/Standard/Strict rules to determine which failures block the workflow and whether overrides are allowed.
Creates an evidence artifact: Writes docs/{feature}/DEPLOY-REVIEW.md summarizing the checklist, verdict, and any blocking remediation steps.

Quick Start

Run wa:deploy-review to scan the current feature context and generate a deploy-readiness PASS/FAIL verdict report for dev-to-main promotion.

Frequently Asked Questions about wa:deploy-review

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

FAQPage Schema

How do I gate dev-to-main deployment readiness with a pass/fail checklist?▼

Dev-to-main deployment readiness gating verifies merge status, validation verdicts, release tags, changelog updates, and tracker issue completion to produce a clear PASS or FAIL verdict. This prevents faulty or incomplete feature branches from being promoted to main.

What is a deploy readiness gate and how does it work for release promotion?▼

A deploy readiness gate enforces a pre-promotion checklist for dev-to-main merges by evaluating stage-based criteria like merge completion and changelog verification. It applies rigor-based rules to determine if failures block the workflow or allow overrides.

How do I generate an auditable deployment review report for a feature branch?▼

Generating an auditable deployment review report involves scanning the current feature context and writing a DEPLOY-REVIEW.md artifact. This document summarizes the deployment checklist, the final gate verdict, and any blocking remediation steps required.

Can I scope deployment readiness checks to a specific feature slug?▼

Yes, deployment readiness checks can be optionally scoped by a feature slug. This targets the validation of merge-to-dev status, release tagging, and tracker issue closure specifically for an individual feature's lifecycle workflow.

What is the difference between Lite, Standard, and Strict rigor levels in deployment gating?▼

Lite, Standard, and Strict rigor levels determine which checklist failures block the dev-to-main workflow and whether overrides are allowed. Higher rigor levels enforce stricter release readiness requirements across merge status, validations, and changelog updates.

Why does my dev-to-main promotion fail the deployment gate despite a successful merge?▼

Dev-to-main promotion fails the deployment gate when release readiness criteria beyond a successful merge are unmet. The gate requires validation verdicts, release tag presence, changelog updates, and tracker issue closure to all pass before allowing promotion.