land-batch

Triage, review, and sequentially merge open PRs with deploy verification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/indigoai-us/hq --skill land-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-batch
Source: https://github.com/indigoai-us/hq/tree/main/template/.claude/skills/land-batch
Command: npx skills add https://github.com/indigoai-us/hq --skill land-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage, review, and land multiple open PRs. Handles CI monitoring, conflict resolution between PRs, Codex-style review, and post-merge deploy verification. Use when asked to "land all PRs", "merge open PRs", or "triage and ship".

Core Features & Use Cases

  • End-to-end PR batching: triage, review, and land multiple PRs in a single batch.
  • Conflict handling: automated conflict resolution when landing PRs in sequence.
  • Deploy verification: post-merge checks across Lambda, SST, and frontend pipelines.

Quick Start

Provide a set of PR numbers or a label filter to begin landing, and the system will triage, review, and merge them sequentially with deploy verification.

Frequently Asked Questions about land-batch

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

FAQPage Schema
How do I merge multiple pull requests in a single batch?

Batching and merging multiple pull requests involves triaging open PRs, enforcing pre-merge CI checks, resolving conflicts sequentially, and verifying post-merge deployments. You provide PR numbers or a label filter to initiate the automated sequential merge process.

What is the best way to handle merge conflicts when landing multiple PRs sequentially?

Handling merge conflicts when landing multiple PRs sequentially requires automated conflict resolution between dependent changes. The system orchestrates sequential merges, continuously validating CI status and resolving conflicts as each PR lands to maintain branch integrity.

How does deploy verification work after merging pull requests?

Deploy verification after merging pull requests executes post-merge runbooks to validate deployment readiness across Lambda, SST, and frontend pipelines. It continuously checks CI status and deployment health to ensure each merged PR successfully reaches production.

Can I use automated PR triage for microservices with deployment blockers?

Automated PR triage for microservices handles deployment blockers by orchestrating review and sequential merges with deploy verification. It enforces pre-merge checks and post-merge runbooks, batching PRs across microservices while managing blockers and CI validation.

Does batch merging open PRs enforce pre-merge CI checks before sequencing merges?

Batch merging open PRs enforces pre-merge CI checks before sequencing any merges. The system continuously validates CI status and deployment readiness, ensuring each pull request passes required checks before it is merged into the target branch.

Why does sequential PR merging fail when CI status is not validated continuously?

Sequential PR merging fails without continuous CI validation because deployment readiness cannot be guaranteed. The system enforces pre-merge checks and post-merge runbooks, continuously validating CI status to prevent broken merges and ensure deployment verification across pipelines.