git-orchestrator

Automate versioning and branch orchestration for private git configuration repositories.

7|3|Updated Jan 15, 2026

Search Tags:#automation #git #branching #orchestration #worktree #session-management #version-control

Ready to run

npx skills add https://github.com/Zpankz/mcp-skillset --skill git-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-orchestrator
Source: https://github.com/Zpankz/mcp-skillset/tree/main/git-orchestrator
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill git-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, bd, bv, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Git-Orchestrator provides meta-level control to manage a private configuration repository by enabling automatic versioning, branch orchestration, and DAG-based issue tracking. It streamlines repo initialization, configuration changes, and history exploration across multiple workstreams and agents.

Core Features & Use Cases

Meta-orchestrator for initializing config repos, committing changes, managing feature branches, creating worktrees, and investigating history.
Integrates with supporting tools (bv, bd, claude-mem) to monitor and automate changes across pillars.
Use Case: Set up a config repo, organize experiments with isolated worktrees, and track configuration history across parallel branches.

Quick Start

Start a new orchestration session by initializing the git-orchestrator workflow and loading the configuration namespace.

Frequently Asked Questions about git-orchestrator

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

FAQPage Schema

How do I automate git branching and worktree management across multiple agents?▼

Git-orchestrator automates git branching and parallel worktree orchestration across multiple agents by coordinating repository initialization, feature-branch creation, and session logging. It enforces structured commit messages and integrates with bv/bd tooling to synchronize changes across isolated worktrees.

What is the best way to maintain automatic versioning in a private git configuration repository?▼

Automatic versioning in a private git configuration repository is maintained through git-orchestrator's meta-level orchestration, which coordinates feature branches and integrates with bv/bd tooling. It enforces structured commit messages and preserves configuration history across parallel workstreams.

Can I use git worktrees to isolate experiments across parallel branches without losing session history?▼

Yes, you can use git-orchestrator to create isolated worktrees for experiments across parallel branches while maintaining robust session logging and history preservation. It coordinates worktrees across multiple agents and tracks configuration changes through DAG-based issue tracking.

Does git-orchestrator work with jq and bd/bv tooling for configuration monitoring?▼

Git-orchestrator integrates directly with bd, bv, and jq dependencies to monitor and automate configuration changes across pillars. It uses these supporting tools to coordinate metadata orchestration, branch management, and automatic versioning within the private repository workflow.

Why should I enforce structured commit messages for feature-branch orchestration?▼

Enforcing structured commit messages during feature-branch orchestration ensures consistent metadata tracking and robust history preservation across parallel worktrees. Git-orchestrator relies on this structure to coordinate DAG-based issue tracking and synchronize changes across multiple agents effectively.

What are the limitations of using git worktrees for multi-agent session management?▼

While git-orchestrator coordinates parallel worktrees across multiple agents, it is specifically designed for private configuration repositories with automatic versioning and requires jq, bd, and bv dependencies. It focuses on structured commit enforcement rather than general-purpose git workflow automation.