land-and-deploy

Merge PRs, wait for CI/CD completion, and verify production via canary checks.

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill land-and-deploy-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack/land-and-deploy
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill land-and-deploy-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually merging PRs, waiting for CI and deployment pipelines to complete, and verifying production health after deployment is time-consuming and error-prone. This skill automates the entire post-PR creation workflow, eliminating manual monitoring and reducing the risk of deploying broken code to production.

Core Features & Use Cases

  • Automated PR Merge: Merges the PR created by /ship once CI checks pass, no manual intervention needed.
  • CI/CD Pipeline Monitoring: Waits for the full deployment pipeline to complete before proceeding.
  • Production Health Verification: Runs canary checks to confirm the deployed feature is working correctly in production.
  • Use Case: After running /ship to create a PR for a new user authentication feature, use this skill to automatically merge the PR, wait for the deploy to finish, and verify no errors are appearing in production canary metrics.

Quick Start

Use the land-and-deploy skill to merge your current open PR, wait for its CI and deployment to complete, and verify production health via 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 PR merge and wait for CI deployment to finish?

Automate PR merge and CI wait by using a post-creation workflow that merges the pull request once CI checks pass and waits for the full deployment pipeline to complete without manual monitoring.

What is automated production health verification after a PR merge?

Automated production health verification runs canary checks after deployment to confirm the newly deployed feature works correctly in production and reports any appearing errors automatically.

How do I stop manually monitoring CI/CD pipelines after creating a PR?

Stop manual CI/CD monitoring by automating the end-to-end post-PR workflow, which handles merge, waits for deployment pipelines, and executes production validation checks independently.

Can I automatically merge a pull request only after CI checks pass?

Yes, you can automatically merge a pull request after CI checks pass by applying an automated Git workflow that gates the merge action on successful CI completion and deployment pipeline status.

Does this deployment workflow support canary checks for production validation?

Yes, the deployment workflow supports canary checks by running production health verification to validate deployed features and capture canary metrics immediately after the deployment pipeline finishes.

What are the limitations of automating Git workflow post-PR deployment?

This automation is limited to Git-based workflows with CI/CD pipelines and canary deployment checks, requiring an existing open PR created via /ship to initiate the end-to-end merge and validation process.