branch-orchestrator

Centralize cross-session git orchestration with deterministic rules from PLATFORM-STATE.yaml.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill branch-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-orchestrator
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/branch-orchestrator
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill branch-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-scoped cross-session orchestration that codifies the decision rules a human orchestrator would otherwise apply by hand. Any agent invokes /branch-orchestrator whenever it would otherwise stop to ask the operator a question that's been answered before. Modes: register (self-register a session at boot), deregister (on ship), decide (consult rules+registry for a verdict), status/ship-order/contention (operator diagnostics), add-rule + add-harmless (extend registries). Reads + writes PLATFORM-STATE.yaml exclusively. Verdicts: PROCEED (with concrete next-step), STOP (with pre-composed user message), or ESCALATE (novel situation; full diagnostic dump). Activates on /branch-orchestrator, branch-orchestrator decide, branch-orchestrator register, what should I do about this git situation, can I ship now, is there a sibling collision, am I safe to rebase.

Core Features & Use Cases

  • Cross-session decision engine that enforces deterministic outcomes for git-state operations.
  • Modes: register, deregister, decide, status, ship-order, contention, add-rule, add-harmless; reads PLATFORM-STATE.yaml and a registry of rules and known errors.
  • Applies governance around git operations across multiple worktrees and products, minimizing operator interruptions.

Quick Start

Invoke /branch-orchestrator decide to obtain a verdict for your pending git operation and follow the guidance.

Frequently Asked Questions about branch-orchestrator

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

FAQPage Schema
How do I automate cross-session git orchestration across multiple worktrees?

Cross-session git orchestration is automated by codifying deterministic decision rules in a PLATFORM-STATE.yaml file, enabling agents to self-register, query decisions, and resolve worktree collisions without manual operator input.

What is a deterministic decision engine for git operations?

A deterministic decision engine for git operations applies codified rules and a known error registry to produce clear verdicts like PROCEED, STOP, or ESCALATE, replacing manual operator judgment for repetitive cross-session scenarios.

Can I use branch-orchestrator to check if I am safe to rebase or ship?

Yes, you can check if you are safe to rebase or ship by invoking the decide mode, which consults your decision rules and session registry to return a PROCEED, STOP, or ESCALATE verdict for your pending git operation.

How do I manage sibling session collisions during git worktree operations?

Sibling session collisions are managed using contention diagnostics and an atomic, lock-protected write process that updates shared platform state, preventing concurrent worktree operations from conflicting.

Do I need a specific file format to enable cross-session git decision automation?

Yes, you need a properly formatted PLATFORM-STATE.yaml file, a defined decision-rule set, and a known_harmless_errors registry to provide the deterministic context required for automated git orchestration.

What limitations exist when automating git state operations with a decision engine?

The decision engine is limited by its registries; novel situations not covered by existing rules or the known_harmless_errors list trigger an ESCALATE verdict, requiring operator intervention and manual rule extension.