land-and-deploy

Featured

Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.

AI & Automation 5,950 stars 774 forks Updated yesterday CC-BY-SA-4.0

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Land and Deploy Complete landing pipeline: merge the PR, wait for CI, verify the deployment, run a health check. Picks up where `/ship` left off. `/ship` creates the PR. This command merges it and verifies production. **Non-interactive by default.** The user said "land it", so land it. Stop only for the critical readiness gate and hard blockers. ## Instructions ### Step 1: Pre-flight ```bash # Verify GitHub CLI is authenticated gh auth status # Detect PR from current branch (or use argument if provided) gh pr view --json number,state,title,url,mergeStateStatus,mergeable,baseRefName,headRefName ``` **Stop conditions:** - GitHub CLI not authenticated → "Run `gh auth login` first" - No PR exists → "No PR found for this branch. Run `/ship` first." - PR already merged → "PR is already merged." - PR is closed → "PR is closed. Reopen it first." --- ### Step 2: CI Status Check ```bash # Check current CI status gh pr checks --json name,state,status,conclusion # Check for merge conflicts gh pr view --json mergeable -q .mergeable ``` **Stop conditions:** - Required checks FAILING → show failing checks, stop - `mergeable` is `CONFLICTING` → "PR has merge conflicts. Resolve them and push before landing." - Required checks PENDING → proceed to Step 3 (wait for CI) - All checks passing → skip to Step 3.5 (readiness gate) --- ### Step 3: Wait for CI (if pending) ```bash # Watch CI checks with 15-minute timeout gh pr checks --watch --fail-fast ``` - CI passes → continue to ...

Details

Author
FlorianBruniaux
Repository
FlorianBruniaux/claude-code-ultimate-guide
Created
8 months ago
Last Updated
yesterday
Language
Python
License
CC-BY-SA-4.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

land

Post-merge landing: take merged MR(s) to verified-in-production by executing the project's landing runbook — watch the main pipeline(s) to green, apply or hand off migrations, deploy in the runbook's order, then canary-verify (health checks, smoke checks) before declaring shipped. Runbook-driven: reads docs/landing.md; on first run it drafts one by inspecting the repo (CI config, migrations, health endpoints) and confirms it with you. Every step is tagged [agent] (executed directly) or [human] (prod-locked — handed to you as exact commands and waited on, never assumed). Hard stops: red pipeline, failed migration, failed canary, unconfirmed human step. Never auto-rolls-back; prepares the revert and asks. Use when: "land this", "deploy the merge", after /ship-feature merges, "take it to prod", running post-merge follow-ups (migrations, deploy order, canary).

0 Updated 1 months ago
ohyesgocool
Code & Development Listed

land

Take a committed branch from local to merged — push it, confirm which GitHub account each tool actually acts as in this repo, open the PR through the one that matches (github-mcp where loaded, gh where its login is confirmed), then fast-forward main and check CI. Use when asked to land, ship or publish a branch, open a pull request, merge to main, or get a branch in; the step after /commit. Use it even when the request already names the mechanism — 'squash these and merge', 'just merge it into main', 'force push it' — a named mechanism is the case these guards exist for, not a reason to skip them. Guards two silent failures: gh and github-mcp can authenticate as different accounts, so a PR lands under the wrong identity with no error, and integration is a local --ff-only merge because a squash would collapse the logical split /commit just made. Stops for confirmation before pushing main. To make the commits first use commit; to review before landing, code-review.

0 Updated today
wardawgmalvicious
AI & Automation Listed

shipit

Land a reviewed pull request: discover the open PR for the current branch, push any unpushed commits, wait for CI to go green, then squash-merge it so the PR title (which may carry a version) lands as the commit subject. Handles a PR that has fallen behind its base (rebase + force-with-lease) and surfaces branch-protection rejections verbatim. Project-agnostic — it knows nothing about how any project versions itself. Invoke ONLY on explicit ship intent — the user says "ship it", "land the PR", "land this", or runs "/shipit". Landing merges, which is irreversible: never infer ship intent from a PR merely being approved, green, or finished.

11 Updated today
bostonaholic