Coordinate Git/GitHub workflows with isolated worktrees and central orchestrator control.
npx skills add https://github.com/HahyeonJeon/gobbi --skill git-hahyeonjeon
Please help me install this Agent Skill. Skill: _git Source: https://github.com/HahyeonJeon/gobbi/tree/main/plugins/gobbi/skills/_git Command: npx skills add https://github.com/HahyeonJeon/gobbi --skill git-hahyeonjeon
Git and GitHub workflows can become error-prone when multiple sessions run concurrently. This skill enforces worktree isolation and central orchestrator control over branches, PR lifecycles, and issues, ensuring isolated task workstreams and predictable integration.
Start a session with the git workflow to initialize worktrees, branches, PRs, and issue tracking using the orchestrator.
High-intent search queries and answers about installing and using this skill.
To manage git worktrees without interference, use an orchestration skill that enforces worktree isolation and central control over branches, PRs, and merges. This ensures isolated task workstreams and predictable integration across concurrent sessions.
Automating the issue-to-merge lifecycle in GitHub requires a central orchestrator to control issue creation, PRs, and merges. Subagents operate inside isolated worktrees to handle branching, CI monitoring, and finish-phase cleanup.
Yes, gh CLI authentication is a required prerequisite for automating GitHub PR workflows. The orchestrator checks prerequisites including remote base syncing and gh CLI authentication before managing worktree lifecycles and PR monitoring.
Handling orphaned worktrees during git workflow automation involves built-in recovery mechanisms managed by a central orchestrator. The orchestrator controls the entire worktree lifecycle, ensuring proper cleanup and preventing session conflicts.
Yes, a central orchestrator can enforce branch naming conventions and manage CI integration. It coordinates the git lifecycle from worktree creation through PR monitoring and cleanup, applying these rules across all concurrent sessions.
Running multiple git branches concurrently causes session interference because standard git workflows lack worktree isolation. Without a central orchestrator controlling pushes and merges, concurrent sessions conflict during branching, PR management, and integration.
bacchus-labsRemove Git worktrees whose linked pull requests have merged while preserving active development branches.
jmylchreestMerge active swarm worktrees into the main branch after testing.
joyco-studioCoordinate parallel Claude Code sessions across git worktrees with deterministic merging.
skaisserRun the flow-auto pipeline in an isolated git worktree and create a PR.
