skills.rest
BaqiF2
BaqiF2COMMUNITY
Explore all skills by this author →
GitHub

merge-pr

Merge GitHub Pull Requests after CI checks and code review pass.

3|Updated Jan 24, 2026
Search Tags:#github#merge#code-review#pull-request#merge-strategy#ci-checks
One-click install
npx skills add https://github.com/BaqiF2/Synapse-Agent --skill merge-pr-baqif2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/BaqiF2/Synapse-Agent/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/BaqiF2/Synapse-Agent --skill merge-pr-baqif2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges GitHub Pull Requests safely by ensuring CI checks pass and code reviews are completed before merging.

Core Features & Use Cases

  • CI verification: Waits for all checks to pass before merge and notifies on pending or failed checks.
  • Mandatory code review: Dispatches a code-reviewer subagent to evaluate changes against the PR description.
  • Merge orchestration: Executes the merge using a chosen strategy, handles conflicts, and cleans up branches post-merge.
  • Use Case: When a PR is ready for production, trigger a safe merge to ensure quality gates are respected.

Quick Start

Ask the AI to merge the PR only after CI checks pass and the code review is complete.

Frequently Asked Questions about merge-pr

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

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

To safely merge a GitHub pull request, the process validates CI status, enforces mandatory code review via subagents, and executes the merge only when all quality gates are respected.

What is the best way to automate pull request code review and merge execution?▼

Automating pull request code review involves dispatching a subagent to evaluate changes against the PR description, followed by merge execution that handles conflicts and cleans up branches post-merge.

Can I choose a specific merge strategy when automating GitHub PR merges?▼

Yes, you can select a merge strategy during merge orchestration, which executes the merge using your chosen method while handling conflicts and performing post-merge branch cleanup.

How does CI verification handle pending or failed checks before a PR merge?▼

CI verification waits for all checks to pass before merging and actively notifies you if any CI checks are pending or have failed, preventing unsafe merges.

What happens if there are merge conflicts during automated GitHub PR merges?▼

During automated GitHub PR merges, the merge orchestration step handles conflict resolution directly, ensuring that the chosen merge strategy executes successfully before branch cleanup.

Do I need a code review subagent to merge PRs across standard repositories?▼

Yes, mandatory code review is enforced by dispatching a code-reviewer subagent to evaluate changes against the PR description, satisfying quality gate requirements across standard PR workflows.

Related Skills

Explore More Software Engineering Skills→
TheFJKTheFJK
2

merge-pipeline

Automate GitHub pull request merging with pre-flight checks and conflict resolution.

Community
Advanced
oabdelmaksoudoabdelmaksoud
4

finishing-a-development-branch

Present merge, PR, keep, or discard options after tests pass.

Community
Advanced
patricio0312revpatricio0312rev
5

quality-gates-enforcer

Enforce CI quality gates for coverage, linting, type checks, and security in Node.js PR workflows.

Community
Advanced
acartineacartine
1

gh_pr_merge

Automate GitHub pull request merges after passing checks with squash merges.

Community
Intermediate