montenegronyc

Backporcher — Git skill for Claude Code

Git community

Parallel Claude Code agent dispatcher: GitHub Issues as task queue, sandboxed worktrees, coordinator review, CI gating, auto-merge.

How to install Backporcher

This entry records only its repository, not the path inside it, so there is no exact command to give. Open montenegronyc/backporcher and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Backporcher does

Parallel Claude Code agent dispatcher: GitHub Issues as task queue, sandboxed worktrees, coordinator review, CI gating, auto-merge.

Alternatives in Git

Worktree Parallel Init — Create multiple git worktrees for parallel development: $ARGUMENTS 23.4k ★
Triage Open Pull Requests — Review, label, and act on all open PRs for a repository using parallel review agents 10.8k ★
Swarm Parent — You are the swarm coordinator for the {{tentacleName}} tentacle 1.4k ★

README

Backporcher

![Backporcher Demo](backporcher_demo_v02.gif)

A fully autonomous software engineering pipeline. Label a GitHub issue with `backporcher`, and in ~20 minutes you get a merged PR with tests passing and the issue closed. A real-time web dashboard lets you manage the fleet: approve or hold tasks before merge, pause/resume the dispatch queue, re-run failed agents, and monitor every stage of the pipeline from triage to merge.

Built in early 2026. 100% auto-merge rate on its first production run (15 PRs, zero manual interventions). This mirrors the agent orchestration architectures emerging from Anthropic's Claude Code and Augment's multi-agent systems, but as a standalone, open-source daemon you can run on your own infra.

What makes it different

Most "AI coding" tools are glorified autocomplete. Backporcher is an **end-to-end pipeline**: it triages, plans dependencies, dispatches sandboxed agents, reviews their work with a coordinator agent, retries CI failures with error context, and merges, all autonomously.

The key insight: treat agents like junior developers. Give them isolated worktrees, review their PRs, and let CI be the final gate. But unlike junior developers, give them a **code-aware navigation map** so they don't waste time exploring the codebase, and feed them **learnings from every past success and failure** in that repo so they get better over time. No magic, just good engineering around `claude -p`.

The Pipeline

GitHub Issue (label: backporcher)
  → Haiku triages complexity (sonnet vs opus)
    → Batch orchestrator assigns priorities + dependency chains
      → Sonnet queries code graph → navigation map of relevant files/symbols
        → Sandboxed claude -p in git worktree (with stack info + learnings + navigation map)
          → Build verification (optional, per-repo)
            → PR created
              → Code graph builds blast radius (Tree-sitter + dependency BFS)
                → Coordinator reviews diff + impacted c