skills.rest
Jeqqe
JeqqeCOMMUNITY
Explore all skills by this author →
GitHub

integrate

Merge CI-green issue branches into one release pull request.

Updated Aug 27, 2026
Search Tags:#git#code review#merge conflicts#dependency resolution#ci validation#github pull request#release integration
One-click install
npx skills add https://github.com/Jeqqe/jersal-project-template --skill integrate-jeqqe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integrate
Source: https://github.com/Jeqqe/jersal-project-template/tree/main/.pi/skills/integrate
Command: npx skills add https://github.com/Jeqqe/jersal-project-template --skill integrate-jeqqe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrate turns multiple already-reviewed, CI-green issue branches into a single coherent release change, preventing seam failures like merge conflicts, cross-module type breakage, and inconsistent behavior only seen when features coexist.

Core Features & Use Cases

  • Fan-in integration: Merges the provided issue branches in dependency order into a new integration branch, resolving mechanical conflicts while stopping for non-mechanical logic conflicts that require a human decision.
  • Assembled-tree validation: Runs the full CI suite against the merged result to catch cross-module breakage that per-branch CI may miss.
  • Combined review and fix loop: Executes a single review pass over the assembled diff, supporting up to a bounded fix loop for blocking review issues.
  • Release-ready PR automation: Opens exactly one PR that closes all included issues and triggers final merge/release flow.

Quick Start

Ask the agent to integrate branches or issue numbers into a single integration branch and open one release PR by running /skill:integrate 1 2 3 4 --into integration/issues-1-2-3-4 --base release.

Frequently Asked Questions about integrate

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

FAQPage Schema
How do I merge multiple feature branches into a single release PR?▼

You can integrate branches by running the command with issue numbers, a target integration branch, and a base branch. This merges the provided branches in dependency order and opens one release pull request.

What is dependency-aware merge order for parallel git branches?▼

Dependency-aware merge order sorts parallel issue branches based on their interdependencies before combining them. This prevents build failures and ensures the assembled tree validates correctly before opening a release pull request.

How do you resolve merge conflicts when integrating multiple branches?▼

The process stops when it detects dependency cycles or non-mechanical logic conflicts that require human decisions. It also blocks integration if any provided branches are missing or not fully ready.

Do I need CI to pass on individual branches before integrating them?▼

After merging branches, the process executes review and fix loops to resolve blocking issues. It then opens exactly one release pull request that closes all included issues and triggers the final merge flow.

Related Skills

Explore More Software Engineering Skills→
GGPromptsGGPrompts
147

brainstorming

Convert vague ideas into structured beads workflows with epics and dependencies.

Community
Basic
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
strawgatestrawgate

follow-the-pr

Monitor GitHub pull request states for CI changes, reviews, and merge readiness.

Community
Advanced
DITEKmaxDITEKmax

ship

Automates a feature branch's test, version, changelog, and PR workflow.

Community
Advanced