skills.rest
rp4ri
rp4riCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

consolidate

Merge multiple green pull requests via a temporary integration branch with conflict exclusion and issue closing.

Updated Jun 4, 2026
Search Tags:#git#github#ci-validation#release-prep#merge-workflow#pull-request-consolidation#conflict-handling
One-click install
npx skills add https://github.com/rp4ri/orchestration-studio --skill consolidate-rp4ri
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: consolidate
Source: https://github.com/rp4ri/orchestration-studio/tree/main/skills/consolidate
Command: npx skills add https://github.com/rp4ri/orchestration-studio --skill consolidate-rp4ri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merging multiple individually green pull requests sequentially to main pollutes the branch with intermediate broken states, risks semantic conflicts between PRs, and fails to auto-close referenced GitHub issues when PRs are merged via an integration branch instead of directly to main.

Core Features & Use Cases

  • Batch PR merging: Combines multiple ready, individually validated PRs onto a temporary integration branch to test the combined state before merging to main.
  • Conflict-aware handling: Automatically excludes PRs that cause merge conflicts from the batch for separate owner handling, with no manual conflict resolution required in the integration branch.
  • Issue closing fix: Explicitly handles the GitHub "Closes #N" gotcha where closing keywords do not fire for PRs merged via integration branches, with post-merge sweep steps to close all referenced issues.
  • Use case: Use this after a parallel development wave produces 4–7 ready PRs, or before a release, to avoid broken main states and ensure all related issues are properly closed.

Quick Start

Use the consolidate skill to merge the batch of ready feature PRs from the current development wave into main via a single integration branch, verify the combined build passes CI, and ensure all referenced issues are closed.

Frequently Asked Questions about consolidate

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

FAQPage Schema
Why do my GitHub issues stay open when merging pull requests via an integration branch?▼

Merging multiple individually green pull requests sequentially risks polluting main with intermediate broken states and semantic conflicts between PRs. Batch PR consolidation onto a temporary integration branch validates the combined state before an atomic merge to main.

How do I safely batch merge multiple pull requests to main without breaking the build?▼

A conflict-aware merge workflow automatically excludes pull requests that cause merge conflicts from the batch for separate owner handling. No manual conflict resolution is required within the temporary integration branch during the consolidation process.

Can I automatically exclude pull requests that cause merge conflicts during batch PR consolidation?▼

Batch PR consolidation combines multiple ready, individually validated PRs onto a temporary integration branch to test the combined state. It is designed for post-parallel-development waves producing 4–7 ready PRs or pre-release integration steps.

What is the best way to consolidate pull requests before a release in Git?▼

The workflow applies combined state validation gates on the temporary integration branch to verify CI passes before merging to main. If CI fails, the batch is withheld to prevent broken main branch states from reaching production.

When should I use an integration branch for merging pull requests?▼

Sequentially merging individually green pull requests to main risks intermediate broken states and semantic conflicts between PRs. Using a temporary integration branch with combined state validation gates delivers an atomic, clean main branch merge.

Related Skills

Explore More Software Engineering Skills→
nsheapsnsheaps
3

update-branch

Synchronize feature branches with their PR base using git and gh.

Community
Advanced
smallorbitsmallorbit

release

Create and merge release PRs, tag commits, close issues, and clean RC branches.

Community
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
dtbuchholzdtbuchholz

sync

Synchronize the current Git branch with origin/main via rebase or pull.

Community
Intermediate