pr-captain-merge

Merge GitHub pull requests with branch protection and principal approval.

39|6|Updated Jan 5, 2026

Search Tags:#automation #git #github #merge #PR #branch protection

Ready to run

npx skills add https://github.com/the-agency-ai/the-agency --skill pr-captain-merge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-captain-merge
Source: https://github.com/the-agency-ai/the-agency/tree/main/.claude/skills/pr-captain-merge
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill pr-captain-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates and safeguards the process of merging pull requests on GitHub, ensuring that only authorized, conflict-free merges occur with full branch protection compliance.

Core Features & Use Cases

Secure Merge Operations: Performs true merge commits without squash or rebase, respecting branch rules and branch protection.
Principal Authorization: Enforces explicit principal approval for bypassing branch protections via --principal-approved.
Use Case: A captain on the main branch in a production environment seamlessly merges approved PRs while maintaining a clean, auditable history, preventing accidental history rewrites.

Quick Start

State the PR number you wish to merge, then issue the command with optional flags such as --principal-approved or --dry-run to simulate the merge without executing it.

Frequently Asked Questions about pr-captain-merge

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

FAQPage Schema

How do I merge a GitHub pull request while respecting branch protection rules?▼

Merging a GitHub pull request while respecting branch protection rules requires a tool that performs true merge commits and enforces principal authorization. This ensures only conflict-free, auditable integrations occur without bypassing branch rules.

Can I simulate a pull request merge on GitHub before executing it?▼

Yes, you can simulate a pull request merge on GitHub before executing it by using a dry-run flag. This allows you to verify that the merge will be conflict-free and compliant with branch protection rules without actually modifying the repository history.

What is the safest way to merge a PR on a protected main branch?▼

The safest way to merge a PR on a protected main branch is to use a process that creates true merge commits without squash or rebase, requires explicit principal approval for bypasses, and maintains a clean, auditable history to prevent accidental history rewrites.

How do I bypass GitHub branch protection rules for an authorized merge?▼

To bypass GitHub branch protection rules for an authorized merge, you must use a specific principal authorization flag. This enforces explicit approval, ensuring the merge is auditable and only performed by an authorized captain when strictly necessary.

Does this merge process use squash or rebase when integrating pull requests?▼

No, this merge process does not use squash or rebase when integrating pull requests. It performs true merge commits to maintain a clean, auditable history and prevent accidental history rewrites in collaborative development workflows.