land-and-deploy

Merge a PR, wait for CI, deploy, and verify production health via canary checks.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mattothomas/sp26_hackpsu --skill land-and-deploy-mattothomas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/mattothomas/sp26_hackpsu/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/mattothomas/sp26_hackpsu --skill land-and-deploy-mattothomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end land-and-deploy workflow. It merges the PR, waits for CI, deploys to production, and verifies health via canary checks to minimize risk.

Core Features & Use Cases

  • End-to-end land and deploy workflow from PR to production health verification.
  • Canary-based production health checks to minimize risk and enable rapid rollback.
  • Post-ship handoffs and PR handoff after successful deployment.

Quick Start

Merge the current PR, wait for CI, deploy to production, and verify health with canary checks.

Frequently Asked Questions about land-and-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate merging a PR and deploying to production?

To automate merging a PR and deploying to production, this Skill handles the end-to-end workflow by merging the PR, waiting for CI, deploying, and verifying production health via canary checks.

What are canary-based production health checks?

Canary-based production health checks are verification steps run after a deployment to minimize risk and enable rapid rollback by monitoring the health endpoints of the newly deployed production environment.

How do I verify production health after a CI deployment?

You can verify production health after a CI deployment by using this Skill to coordinate with health endpoints and execute canary checks, ensuring the deployment is stable before completing post-ship handoffs.

Can I use a PR URL to trigger an automated merge and deploy workflow?

Yes, you can use a PR URL or PR number to trigger the automated merge and deploy workflow, which then waits for CI, deploys to production, and handles post-ship handoffs deterministically.

What is the best way to handle post-ship handoffs after a production release?

The best way to handle post-ship handoffs after a production release is to automate them as part of the land-and-deploy workflow, ensuring logs telemetry and PR handoff occur successfully after health verification.