land

Monitor CI checks, resolve conflicts, and squash-merge GitHub pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/grafana/sigil --skill land-grafana
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/grafana/sigil/tree/main/.agents/skills/land
Command: npx skills add https://github.com/grafana/sigil --skill land-grafana

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of merging code changes into the main branch by ensuring all automated checks pass and conflicts are resolved, reducing manual oversight and potential merge errors.

Core Features & Use Cases

  • Automated PR Merging: Monitors Pull Requests, waits for CI checks to pass, and performs a squash-merge.
  • Conflict Resolution: Integrates with gh CLI to check for and help resolve merge conflicts.
  • Review Feedback Handling: Manages feedback from bots like Codex and Bugbot, ensuring issues are addressed before merging.
  • Use Case: When you've finished coding a feature, you can ask this Skill to "land the PR," and it will handle the entire process of getting it merged into the main branch without further intervention.

Quick Start

Use the land skill to merge the current pull request after all checks pass.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automatically merge a GitHub pull request after CI checks pass?▼

To automatically merge a GitHub pull request, you can use an automation tool to monitor CI checks, resolve conflicts, and perform a squash-merge once all tests succeed. This ensures code quality and stability without manual intervention.

What is the best way to handle merge conflicts when landing a pull request?▼

The best way to handle merge conflicts when landing a pull request is using an automated script that integrates with the `gh` CLI to detect and help resolve conflicts before attempting a squash-merge.

Do I need the `gh` CLI authenticated to automate squash-merging my code?▼

Yes, you need the `gh` CLI authenticated to automate squash-merging your code. The automation operates on the current Git branch context and relies on the CLI to monitor checks and interact with the repository.

How does automated code review feedback from bots like Codex and Bugbot get handled before merging?▼

Automated code review feedback from bots like Codex and Bugbot is handled by managing their inputs and ensuring all reported issues are addressed before the pull request is merged into the main branch.

Can I automate squash-merging a pull request while waiting for CI/CD pipelines to finish?▼

Yes, you can automate squash-merging a pull request while waiting for CI/CD pipelines. The process specifically monitors CI checks and only executes the merge after verifying that all automated tests have passed.