merge

Merge GitHub pull requests after verifying clean tree, checks, and review.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/dallenpyrah/pi --skill merge-dallenpyrah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/dallenpyrah/pi/tree/main/skills/merge
Command: npx skills add https://github.com/dallenpyrah/pi --skill merge-dallenpyrah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of merging a Pull Request (PR) on GitHub after a learning file has been committed and pushed, ensuring a clean tree, passing checks, and reviewability.

Core Features & Use Cases

  • Automated PR Merging: Merges a PR after a learning file is committed and pushed.
  • Clean Tree Verification: Ensures the working tree is clean before merging.
  • Check Passing Verification: Verifies that required checks are passing before merging.
  • Review Verification: Ensures the PR has been reviewed before merging.
  • Merge Strategy: Defaults to squash, but can adapt to repository's merge queue requirements.
  • Use Case: Ideal for teams that want to streamline their PR workflow, reducing manual intervention and ensuring quality.

Quick Start

Run the '/merge' command after '/learn' has completed and the learning file has been pushed.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate GitHub pull request merging with checks and review verification?

Automating pull request merging requires verifying a clean working tree, confirming required checks pass, and ensuring review status is met before merging. This Skill handles these GitHub PR verification steps automatically using the gh CLI.

What's the best way to ensure a clean Git tree before merging a PR?

Ensuring a clean Git tree before merging a PR involves checking the working tree status to prevent conflicts. This Skill automates clean tree verification as a prerequisite step before proceeding with any GitHub pull request merge.

Does this automated PR merge workflow require the GitHub CLI?

Yes, this automated PR merge workflow requires the gh CLI for GitHub API interaction. The gh command-line tool is a necessary dependency to verify checks, fetch review status, and execute the pull request merge.

Can I use squash and merge strategy for GitHub pull requests automatically?

Yes, you can use the squash merge strategy for GitHub pull requests automatically. This Skill defaults to squash merging but can adapt to a repository's specific merge queue requirements if a different strategy is configured.

Why does my automated PR merge fail when GitHub Actions checks are still running?

An automated PR merge fails when GitHub Actions checks are still running because this Skill enforces check passing verification. It ensures all required CI checks complete successfully before attempting to merge the pull request.

What limitations exist when automating GitHub PR merges across different repository strategies?

Limitations when automating GitHub PR merges include dependency on the gh CLI and strict requirements for a clean tree, passing checks, and completed reviews. It adapts to repository merge queue strategies but cannot bypass these enforced quality gates.