Merge pull requests, wait for CI, and verify production health via canary checks.
npx skills add https://github.com/ibalasite/gstack --skill land-and-deploy-ibalasite
Please help me install this Agent Skill. Skill: land-and-deploy Source: https://github.com/ibalasite/gstack/tree/main/land-and-deploy Command: npx skills add https://github.com/ibalasite/gstack --skill land-and-deploy-ibalasite
Land-and-deploy automates the fragile, error-prone steps between creating a PR and confirming a successful production rollout, removing manual waiting, guesswork, and unsafe merges.
Run the land-and-deploy skill on your branch by invoking /land-and-deploy #PR_NUMBER or /land-and-deploy <url> to merge the PR, wait for CI and deploy, and verify production health.
High-intent search queries and answers about installing and using this skill.
Automating a GitHub pull request merge and production health verification involves merging the branch via GitHub CLI, monitoring CI and CD pipelines until completion, and running canary health checks against your production endpoint to confirm rollout safety.
Canary checks verify production deployments by performing HTTP health checks against a provided URL or detected production endpoint after the deploy pipeline finishes, determining if the rollout is healthy or if a revert is necessary.
The safest way to merge a feature branch and wait for CI-driven deploy pipelines is to perform an initial dry-run, enforce pre-merge readiness gates for reviews and tests, and stop automatically on authentication errors, conflicts, or failing CI.
Yes, authenticated GitHub CLI access is required to automate PR merges and deployments, as the process relies on the CLI to land branches, monitor CI pipelines, and trigger subsequent deployments safely.
If a canary health check fails after a production deploy, the automated workflow reports a BLOCKED outcome and provides revert guidance to help the release engineer safely roll back the changes.
You cannot trigger a production rollback automatically, but the workflow stops safely on failing CI and provides explicit revert guidance if canary health checks fail, leaving the final revert decision to the release engineer.
FirzusMonitor GitHub pull requests for CI, reviews, mergeability, and conflicts.
hamzaPixlVerify deployments with post-merge canary checks against a target URL.
tropeksCoordinate PR merge, CI checks, production deployment, and canary verification.
VertaKhanMerge a PR, wait for CI, deploy to production, and verify canary health.
