skills.rest
dimakis
dimakisCOMMUNITY
Explore all skills by this author →
GitHub

land-pr

Shepherd GitHub pull requests through CI checks, reviews, and squash merges.

Updated Mar 31, 2026
Search Tags:#code review#pull request#github#gh cli#ci checks#merge automation
One-click install
npx skills add https://github.com/dimakis/mitzo --skill land-pr-dimakis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-pr
Source: https://github.com/dimakis/mitzo/tree/main/skills/land-pr
Command: npx skills add https://github.com/dimakis/mitzo --skill land-pr-dimakis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you shepherd a pull request from open to merged by enforcing a strict sequence of passing CI checks and addressing review feedback before merging.

Core Features & Use Cases

  • CI gatekeeping: Watches PR checks and retrieves failing logs to drive targeted fixes.
  • Review feedback loop: Detects pending reviews, reads each comment’s context, applies fixes, and waits for the next approval cycle.
  • Merge finalization: Merges only after CI is green and sufficient review rounds are approved.

Quick Start

Ask the AI to land PR 123 in your repository, ensuring CI is green and all review findings are fixed before performing the final merge.

Frequently Asked Questions about land-pr

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

FAQPage Schema
How do I merge a GitHub pull request only after CI checks pass and reviews are approved?▼

To merge a pull request safely, you must shepherd it by watching CI checks, addressing code review feedback iteratively, and performing a squash-merge only after all approvals are received and CI is green.

What is the best way to handle code review feedback and failing CI checks before merging a PR?▼

Handling code review feedback and failing CI checks requires retrieving failing logs to drive fixes, reading review comments for context, applying targeted commits, and waiting for the next approval cycle before merging.

How do I automate watching CI checks and iterating on review comments using GitHub CLI?▼

You can automate PR shepherding by using GitHub CLI to watch checks, inspect review and comment APIs, iteratively apply fixes with commits and pushes, and merge only after approvals and green CI.

Does this PR merge process support squash-merge semantics when addressing review comments?▼

Yes, the PR merge process applies squash-merge semantics when addressing review comments, ensuring commits are consolidated when finalizing the merge after CI pass-through and multi-round code reviews.

Why does my pull request require multiple rounds of code review before final merge?▼

Your pull request requires multiple review rounds because the shepherding process enforces a strict sequence of addressing review feedback and passing CI checks before finalizing the merge.

Can I use this approach to land a PR in repositories that require multi-round code review and CI pass-through?▼

Yes, this approach specifically applies to repositories that require CI pass-through and multi-round code review, enforcing a strict sequence of fixes and approvals before completing the merge.

Related Skills

Explore More Software Engineering Skills→
brandonalfredbrandonalfred
2

draft-pr

Create and push draft pull requests from GitHub feature branches.

Community
Intermediate
LaPaGaYoLaPaGaYo

deploy

Automate end-to-end deployment workflows with health checks and release gating.

Community
Advanced
googlegoogle
291

Push to GitHub

Run unit tests and lint checks before pushing changes to GitHub.

Official
Intermediate
HabibTorjmenHabibTorjmen

merge-train-infra

Document GitHub Actions automation internals for merge-train operations.

Community
Advanced