dbggr

Bunker — Git skill for Claude Code

Git community

Label a GitHub issue, get back a reviewed, tested, merged pull request: Claude coding agents in sandboxed git worktrees.

How to install Bunker

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

What Bunker does

Label a GitHub issue, get back a reviewed, tested, merged pull request: Claude coding agents in sandboxed git worktrees.

Alternatives in Git

Clean Worktrees (Automatic) — Automatically remove all worktrees for branches merged into master 25.5k ★
Worktree Deliver — Commit all work, push, and create a pull request from the current worktree 23.4k ★
Yeet — Stage, commit, push code, and open a GitHub pull request via CLI 14.6k ★

README

bunker

**Label a GitHub issue. Get back a reviewed, tested, merged pull request.**

bunker runs a Claude coding agent on each issue in its own git worktree and Docker sandbox, has a second agent review the change, runs your tests, and lets GitHub's own required checks decide what merges. You choose the work; bunker does it, and stops to ask when it should.

**Status: beta (v0.12.0).** bunker works its own repository every day (most of its code was written by bunker), but flags, config keys and labels can still change before 1.0. Progress to 1.0: the [v1.0.0 milestone](https://github.com/dbggr/bunker/milestone/1) and [release/v1-readiness.md](release/v1-readiness.md).

How it works

You label an issue bunker:queued. Only repo admins and maintainers can queue work; bunker checks who added the label.
An agent writes the change in a sandbox: a fresh git worktree and a Docker container that never sees your GitHub token or SSH keys.
A second agent reviews it and sends it back with required changes, for up to a few rounds.
Your tests run in the sandbox with no network and no credentials. If they fail, the agent gets one fix round.
bunker opens a PR and arms GitHub auto-merge. It merges only when the branch's required status check passes. Changes to CI, bunker's own config or agent instructions always wait for a person; anything it can't finish is labelled bunker:failed with the reason.

Requirements

Linux or macOS with Docker, git and [Bun](https://bun.sh); the [GitHub CLI](https://cli.github.com) logged in; [Claude Code](https://docs.claude.com/en/docs/claude-code/setup) with a Claude subscription or API key; a fine-grained GitHub token (Contents, Pull requests, Issues read/write; Metadata read; *no* Workflows); and a repo with tests and a CI check required by a GitHub **ruleset**. `bunker init` walks you through all of it.

**Cost:** agent runs are billed to your Claude plan or API account. On this repository the average