land-and-deploy

Coordinates automated release workflow from PR merge to canary health validation.

Updated Apr 6, 2025
One-click install
npx skills add https://github.com/yolopunk/jedi --skill land-and-deploy-yolopunk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/yolopunk/jedi --skill land-and-deploy-yolopunk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates a mostly automated end-to-end release workflow: it merges a PR, waits for CI, deploys to production, and verifies health via canaries.

Core Features & Use Cases

  • End-to-end PR merge, deployment, and production health verification with optional canary checks.
  • Pre-merge readiness and CI-check guards, plus fallbacks for merge conflicts and degraded deployments.
  • Deploy strategy detection and verification across common platforms, with optional persisted configs and canary URL validation.

Quick Start

Trigger the end-to-end flow by running the /land-and-deploy command on a ready PR to initiate merge, deploy, and canary verification.

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 PR merge, CI checks, and production deployment in one workflow?

You can automate PR merge and production deployment by triggering an end-to-end workflow that merges your PR, waits for CI, deploys, and validates production health. It coordinates pre-flight checks, merge safety, and deploy verification across GitHub-based projects.

What is canary health verification in a CI/CD release workflow?

Canary health verification in a release workflow validates production stability after deploying by checking canary URLs or workflow-based metrics. This ensures the new deployment is healthy before completing the automated release process.

Do I need GitHub CLI authentication to merge PRs and verify production deployments?

Yes, GitHub CLI authentication is a required prerequisite. The automated deployment workflow enforces GitHub CLI authentication to handle PR state checks, merge operations, and deploy verification on feature branches.

Can I detect and apply different deploy strategies across platforms during PR merge automation?

Yes, the PR merge automation includes configurable deploy strategy detection across common platforms. It applies platform-specific verification methods, including optional canary URL validation and workflow-based checks.

What happens if there are merge conflicts or degraded deployments during automated release?

The automated release workflow includes fallbacks for merge conflicts and degraded deployments. If production health checks fail or conflicts occur, the workflow halts to prevent unsafe merges and ensure deployment stability.

When should I use an end-to-end merge and deploy workflow instead of manual releases?

Use an end-to-end merge and deploy workflow when you need automated CI waiting, merge safety guards, and canary health checks for GitHub-based projects. It replaces manual releases when consistent production validation is required.