merge-pr

Name: merge-pr
Availability: InStock
Author: TalonT

Merge GitHub pull requests into the integration branch with conflict reports.

5|1|Updated Feb 18, 2026

Search Tags:#git #ci/cd #pull request #github #merge #conflict resolution

Ready to run

npx skills add https://github.com/TalonT-Org/AutoSkillit --skill merge-pr-talont-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/merge-pr
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill merge-pr-talont-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of merging pull requests into a main integration branch, handling both simple merges and complex conflict scenarios to maintain code integrity.

Core Features & Use Cases

Automated Merging: Uses gh pr merge --squash --auto for simple PRs, ensuring status checks pass before merging.
Conflict Detection & Reporting: For complex PRs, it analyzes potential conflicts with the integration branch and generates a detailed conflict report for manual resolution.
Deletion Regression Scan: Identifies and flags PRs that reintroduce deleted code, preventing accidental regressions.
Use Case: In a CI/CD pipeline, this skill is used to process a queue of incoming PRs, merging them sequentially or flagging those that require manual conflict resolution.

Quick Start

Merge the pull request with number 123 into the current branch.

Frequently Asked Questions about merge-pr

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

FAQPage Schema

How do I automatically merge a GitHub pull request into an integration branch?▼

To automatically merge a GitHub pull request, the Skill uses the gh pr merge command with squash and auto flags, enforcing that all required status checks pass before the integration branch accepts the changes.

What happens when there are merge conflicts in a pull request?▼

When complex conflict scenarios arise, the Skill analyzes potential conflicts against the integration branch and generates a detailed conflict report to guide manual resolution rather than forcing the merge.

Can I prevent deleted code from being reintroduced during a pull request merge?▼

Yes, the Skill performs a deletion regression scan to identify and flag pull requests that reintroduce deleted code, preventing accidental regressions from entering the integration branch.

Does this pull request merge tool work in a CI/CD pipeline?▼

The Skill is designed for CI/CD pipelines to process a queue of incoming pull requests, providing structured output for pipeline routing by either merging sequentially or flagging for conflict resolution.

Why does a pull request fail to merge even when status checks pass?▼

A pull request may fail to merge if the deletion regression scan detects reintroduced deleted code, or if complex conflict scenarios require manual resolution despite passing standard status checks.