merge-pr

Verify CI checks, detect conflicts, and squash-merge approved pull requests.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Develonaut/bnto --skill merge-pr-develonaut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/Develonaut/bnto/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/Develonaut/bnto --skill merge-pr-develonaut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify and merge pull requests into main to ensure safe integration by validating CI, detecting conflicts, and auditing descriptions. This skill coordinates CI verification, conflict checks, and description accuracy before merging, reducing risk of faulty merges.

Core Features & Use Cases

  • CI gate verification: ensures required status checks pass before merge.
  • Conflict detection: identifies merge conflicts and guides resolution.
  • Description auditing: compares PR body to changes to ensure accurate communication.
  • Merge workflow: applies a squash merge by default after approval, with support for other strategies.

Quick Start

Initiate the merge-pr process by validating CI, confirming mergeability, and applying the chosen merge strategy.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I verify CI status checks and merge a pull request safely in GitHub?

To verify CI status checks and merge a pull request safely, this skill coordinates CI gate verification, conflict detection, and description accuracy auditing before applying a squash merge pathway into the main branch.

What is the best way to detect merge conflicts before integrating a pull request?

The best way to detect merge conflicts before integrating a pull request is using automated conflict detection that identifies issues and guides resolution, ensuring PRs are fully ready for safe integration into the main branch.

Can I enforce description accuracy auditing when merging GitHub pull requests?

Yes, you can enforce description accuracy auditing when merging GitHub pull requests. The skill compares the PR body to the actual changes to ensure accurate communication before the merge pathway is initiated.

Does this pull request merge workflow support strategies other than squash merge?

This pull request merge workflow applies a squash merge by default after CI gate checks and conflict detection pass, but it also includes support for configuring other merge strategies within GitHub workflows.

What happens if required CI gate checks fail during pull request verification?

If required CI gate checks fail during pull request verification, the integration is halted. The skill ensures required status checks must pass before merge, reducing the risk of faulty merges into the main branch.