integrate

Rebase session and memory Git branches onto main with conflict reporting.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill integrate-kord96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrate
Source: https://github.com/Kord96/kordinate/tree/main/shared/skills/integrate
Command: npx skills add https://github.com/Kord96/kordinate --skill integrate-kord96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile transient session or memory Git branches into main while making conflicts and cleanup explicit, preventing accidental force-pushes or hidden background mutations to user worktrees. The Skill centralizes safe integration workflows so operators can merge completed agent work or session edits without risking active processes or losing commits.

Core Features & Use Cases

  • Discover and classify session/* branches in the current repository or memory/* branches in KORDINATE_HOME, skipping active or empty branches.
  • Integrate changes using a detached-HEAD integration workspace, rebase onto latest main, and fast-forward main with explicit push or local update for memory branches.
  • Provide clear conflict reporting, avoid guessing on complex merges, and perform explicit cleanup of worktrees and local branches after successful integration.
  • Use Case: Consolidate outputs from multiple ephemeral agent worktrees or user sessions into a single main branch while preserving safety and visibility.

Quick Start

Run the integrate skill with optional --memory or a specific branch name to reconcile branches into main, report conflicts, and clean up merged worktrees.

Frequently Asked Questions about integrate

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

FAQPage Schema
How do I safely merge Git worktree branches into main without force-pushes?

Safe branch merging uses a detached-HEAD integration workspace to rebase session or memory branches onto main, fast-forwarding updates while enforcing no force-push to main. This prevents accidental data loss and provides explicit conflict reporting during integration.

What is a detached-HEAD integration worktree for branch reconciliation?

A detached-HEAD integration worktree is an isolated Git workspace that reconciles session and memory branches with main by fetching origin main and rebasing changes. It surfaces conflicts explicitly without mutating active agent worktrees or risking hidden background changes.

How do I consolidate multiple ephemeral agent worktrees into a single main branch?

Consolidating ephemeral agent worktrees involves discovering session/* branches, skipping active or empty ones, and rebasing them onto latest main within a detached-HEAD workspace. It fast-forwards main and performs explicit worktree cleanup after successful integration of completed agent work.

Does this branch integration workflow skip active Git worktrees to protect running sessions?

Yes, the integration workflow discovers and classifies session/* and memory/* branches, actively skipping those marked as active or empty. This protects running agent sessions from hidden background mutations while safely merging only completed worktrees into main.

What happens when conflict resolution is needed during a branch rebase onto main?

When conflict resolution is needed during a branch rebase onto main, the integration process provides clear conflict reporting and avoids guessing on complex merges. Operators receive explicit conflict details within the detached-HEAD workspace to resolve them manually.

Can I integrate memory branches stored outside my current Git repository?

Yes, memory/* branches stored under KORDINATE_HOME can be integrated by targeting them during the reconciliation process. The workflow applies local updates to these memory branches and performs explicit cleanup after merging them into main.