pr-merge-workflow

Automate GitHub pull request review and merging across target branches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/imaginationeverywhere/clara-code --skill pr-merge-workflow-imaginationeverywhere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-merge-workflow
Source: https://github.com/imaginationeverywhere/clara-code/tree/main/.cursor/skills/pr-merge-workflow
Command: npx skills add https://github.com/imaginationeverywhere/clara-code --skill pr-merge-workflow-imaginationeverywhere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating and merging multiple pull requests into the correct target branches can be error-prone and time-consuming; this skill standardizes the review-to-merge workflow and reduces manual steps.

Core Features & Use Cases

  • Single PR Merge: Review, validate CI, and squash or merge into main or develop with automated branch deletion.
  • Batch PR Merge: Gather multiple approved PRs and merge them in sequence with consistent policies.
  • Conflict Handling: Detect and resolve merge conflicts with guided prompts and safe fallbacks.
  • Use Case: A team has 5 PRs ready for main; run this skill to merge them in a single operation after CI passes.

Quick Start

Manually trigger a merge operation across main or develop, or run a batch merge for multiple PRs with CI checks.

Frequently Asked Questions about pr-merge-workflow

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

FAQPage Schema
How do I automate GitHub pull request merges across multiple branches?

Automating GitHub pull request merges across branches is handled by standardizing the review-to-merge workflow with CI checks and conflict handling. It applies to single merges, batch processing, and worktree-to-PR flows using gh pr commands.

Can I merge multiple approved pull requests into main in a single operation?

You can merge multiple approved pull requests into main in a single operation using batch processing. This gathers approved PRs and merges them in sequence with consistent policies after CI validation passes.

How does conflict handling work when merging GitHub pull requests?

Conflict handling when merging GitHub pull requests works by detecting merge conflicts and resolving them through guided prompts with safe fallbacks. This prevents failed merges during automated batch processing or single PR operations.

What is the best way to streamline PR reviews and merges for a development team?

The best way to streamline PR reviews and merges is to automate the review-to-merge workflow, reducing manual steps and errors. It validates CI, squashes or merges into target branches, and performs automated post-merge branch deletion.

Does this PR merge workflow require specific GitHub branch targets?

The PR merge workflow supports specific GitHub branch targets like main or develop. You can manually trigger merge operations across these target branches while ensuring CI checks pass before integration.

What happens to branches after a pull request is merged?

After a pull request is merged, post-merge cleanup performs automated branch deletion. This removes the source branch to maintain a clean repository state following the squash or merge operation into the target branch.