Merge GitHub pull requests, wait for CI, and verify production health.
npx skills add https://github.com/24601/gastack-pre-fork --skill land-and-deploy-24601
Please help me install this Agent Skill. Skill: land-and-deploy Source: https://github.com/24601/gastack-pre-fork/tree/main/land-and-deploy Command: npx skills add https://github.com/24601/gastack-pre-fork --skill land-and-deploy-24601
Land-and-deploy automates the risky, repetitive steps of merging a pull request, waiting for CI and deployment, and verifying production health so releases do not silently break users. It reduces manual monitoring, guesswork, and the chances of a bad merge reaching production by enforcing readiness gates and canary checks.
Run /land-and-deploy to merge the current PR, wait for CI and deployment, and verify production health at the optional URL you provide.
High-intent search queries and answers about installing and using this skill.
Automating a GitHub PR merge, CI wait, and production deploy involves merging via GitHub CLI, monitoring deploy workflows, and running canary health checks. This Skill enforces readiness gates to prevent bad merges from silently breaking users.
If CI fails or merge conflicts occur during an automated deploy, the process halts and reports the specific issue. It handles CI failures, permission errors, and merge conflicts while offering rollback or revert actions to restore production health.
Canary health checks verify production after a GitHub deployment by querying an optional production URL. The process performs post-deploy verification, reports any detected issues with evidence, and offers rollback options if problems are found.
Yes, you need GitHub CLI authentication and access to the repository's workflows to merge and deploy pull requests automatically. An optional production URL is also required for post-deploy verification and canary health checks.
Yes, you can run a dry validation before merging a pull request to production. A first-run dry-run executes automatically on initial use and whenever deploy configuration changes, requiring explicit confirmation for risky steps.
The best way to roll back a bad GitHub release after deployment is to use automated canary checks that detect issues and offer revert actions. This provides clear failure handling and rollback options when production health checks fail.
fghaffarMerge PRs, wait for CI, deploy, and verify production health in GitHub workflows.
mattothomasMerge a PR, wait for CI, deploy, and verify production health via canary checks.
bRRRITSCOLDAutomate CI/CD pipeline creation and management with GitHub Actions.
timurgaleevMerge PRs, trigger deployments, and validate production health via canaries.
