land

Finish a GitHub pull request to a mergeable, green state.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dmooney/Rundale --skill land-dmooney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/dmooney/Rundale/tree/main/.agents/skills/land
Command: npx skills add https://github.com/dmooney/Rundale --skill land-dmooney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably land a specific pull request by resolving conflicts, addressing unaddressed bot review threads, and fixing failing CI so the PR can be merged safely.

Core Features & Use Cases

  • End-to-end PR finishing: Selects the target PR (by argument or current branch), validates mergeability/gates, and performs the final squash merge.
  • Conflict resolution and correctness checks: When the PR is dirty or behind, it merges in a clean worktree, resolves conflicts file-by-file, and requires just check to pass before pushing.
  • Bot feedback closure: Finds unresolved non-outdated bot review threads and either fixes the underlying issues or posts a dismissive explanation and then resolves the threads.
  • CI stabilization: Diagnoses failed checks, distinguishes real failures from transient workflow issues, and retries or retriggers CI until all required checks are green.
  • Use Case: When your PR is almost ready but CI is red and bots left threads unresolved, this Skill drives the PR through every final cleanup step until it is merge-ready.

Quick Start

Tell the assistant: "Land #842 and squash-merge it once all checks are green."

Frequently Asked Questions about land

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

FAQPage Schema
How do I resolve merge conflicts and fix failing CI checks on a GitHub pull request?

To resolve merge conflicts and fix failing CI checks on a GitHub pull request, this Skill merges the target PR in a clean worktree, resolves file conflicts, runs correctness checks, and retries CI until all required checks pass.

What is the best way to squash merge a PR with unaddressed bot review threads?

The best way to squash merge a PR with unaddressed bot review threads is to automatically resolve non-outdated bot comments, either by fixing the underlying issues or posting a dismissive explanation, before performing the final merge.

Can I land a pull request that is behind main without rebasing?

Yes, you can land a pull request that is behind main without rebasing. This Skill merges the main branch into your PR within a clean worktree to resolve conflicts and bring it to a mergeable state.

How do I automatically dismiss unresolved bot review threads before merging a GitHub PR?

To automatically dismiss unresolved bot review threads before merging a GitHub PR, this Skill identifies non-outdated automated comments, posts a dismissive explanation, and resolves the threads so the PR can be squash merged.

What steps are needed to stabilize transient CI failures before a squash merge?

To stabilize transient CI failures before a squash merge, this Skill diagnoses failed GitHub checks, distinguishes real failures from transient workflow issues, and retries or retriggers CI until all required checks are green.

Does this PR finishing workflow require passing local correctness checks before pushing?

Yes, this PR finishing workflow requires passing local correctness checks before pushing. It runs `just check` after resolving merge conflicts to ensure the code is stable before attempting the final squash merge.