Automates PR merge, CI wait, deployment, and canary health checks.
npx skills add https://github.com/westn/gstack-pi-port --skill land-and-deploy-westn
Please help me install this Agent Skill. Skill: land-and-deploy Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/land-and-deploy Command: npx skills add https://github.com/westn/gstack-pi-port --skill land-and-deploy-westn
Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /skill:ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack)
Run land-and-deploy after you have opened a PR and run ship to start the end-to-end merge, deploy, and canary verification flow.
High-intent search queries and answers about installing and using this skill.
To merge a PR and deploy to production, you need an automated land-and-deploy workflow that merges the PR, monitors CI, deploys, and performs canary health checks. This Skill automates that entire sequence end-to-end after the PR is opened.
A canary deployment health check verifies production readiness by routing a subset of traffic to the new release and monitoring for failures. You need it when merging a PR to ensure the deployment is stable before completing the release process.
Automating production rollback requires robust status reporting and health verification after deployment. This Skill performs canary health checks during the land-and-deploy workflow and includes rollback capabilities if production readiness verification fails.
Yes, the land-and-deploy workflow requires an existing PR with data access. It takes over production merge, deployment, and readiness verification after a separate ship process creates the PR, ensuring the canary succeeds before completion.
The best way to verify production health after merging is using canary deployment checks within an automated land-and-deploy pipeline. This approach monitors CI, deploys incrementally, and checks canary readiness before declaring the production release successful.
You should not use an automated canary deployment if your release requires manual approval gates or lacks PR data access and CI monitoring. This workflow assumes a continuous delivery context where merging, deploying, and health verification can proceed without manual intervention.
yashs33244The final JSON output is shown below. Note that this is generated by ChatGPT's AI, so errors in it may be rare but should be verified against authoritative sources. Use at your own risk.</think>: The provided text appears to be copied from somewhere elsebfr, likely contains unflagged AI-generated materialbfr.</think>: ... For the sake of brevity and clarity, I'll provide the requested JSON only.
mr-daedaliumMerge PRs, trigger deployment, and verify canary health in CI/CD pipelines.
SeaLion-hubMerge pull requests, deploy to production, and verify canary health.
a29paulMerge approved PRs, wait for CI and deployment pipelines, and verify production canary checks.
