production-gate

Production deployment gating automates readiness checks by querying GitHub issues and merge status to validate test completion, pending changes, and confirmations. The Skill evaluates these blockers and outputs a deployable or non-deployable decision with rationale, eliminating manual gate reviews.

A deployment gate checks for test-related issues awaiting fixes, pending change requests, and confirmation holds. It validates that all blockers are resolved and the merge is complete, then reports deployment readiness with specific reasons for any blocks.

Yes, deployment gating integrates into GitHub-hosted CI/CD workflows. It fetches issue states and merge readiness from GitHub, applies filtering logic to identify deployment blockers, and emits a standardized gate report to inform automated or manual deployment decisions.

When all checks pass, the deployment gate outputs a deployable status with a release-notes draft summarizing the validated changes. When blockers exist, it returns non-deployable status with specific reasons and remediation suggestions.

Deployment gates run automatically within CI/CD pipelines. The Skill queries GitHub directly, evaluates test and merge readiness autonomously, and emits gate decisions without requiring manual issue review or status aggregation.