Merge PRs, deploy to production, and verify health with canary checks.
npx skills add https://github.com/imonmi/INTER-EDU --skill land-and-deploy-imonmi
Please help me install this Agent Skill. Skill: land-and-deploy Source: https://github.com/imonmi/INTER-EDU/tree/main/gstack-main/gstack-main/land-and-deploy Command: npx skills add https://github.com/imonmi/INTER-EDU --skill land-and-deploy-imonmi
Land-and-deploy automation streamlines the release process by merging PRs, waiting for CI, deploying to production, and validating health with canary checks, reducing manual handoffs and errors.
Invoke /land-and-deploy to auto-detect the PR for your current branch and start the end-to-end release flow
High-intent search queries and answers about installing and using this skill.
Automating PR merge and deployment after CI passes is handled by an end-to-end release workflow that merges the PR, waits for CI, deploys, and validates production health with canary checks, reducing manual handoffs and errors.
A canary deployment check verifies production health by monitoring the newly deployed release. The workflow performs canary validation post-deployment and provides rollback options if the health checks fail.
To rollback a deployment when health checks fail, the land-and-deploy workflow includes automated rollback options during the canary validation phase. It prompts for decisions and logs telemetry for auditing the failure.
Yes, you can use GitHub CLI workflows to auto-detect the PR for your current branch. Invoking the land-and-deploy flow starts the end-to-end release process, proceeding through merge, deploy, and canary validation.
Running an end-to-end release workflow with canary validation relies on standard tooling such as Bash, Read, Write, Glob, and AskUserQuestion to coordinate checks, prompt for decisions, and log telemetry for auditing.
You should not use an automated land-and-deploy workflow when your release requires manual intervention outside standard CI checks or lacks canary infrastructure, as the workflow depends on automated health verification and rollback options.
D0NMEGAPush a branch, create a PR with an auto-generated body, and track merge status.
CODE-SAURABHVerify production deployments and canary releases for health and performance regressions.
k2worksOrchestrate environment setup, IaC provisioning, CI/CD pipelines, and deployment workflows.
aimasteraccMerge PRs after CI passes and trigger production deployment with canary health checks.
