Branch

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

37 stars 7 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill branch
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/branch ~/.claude/skills/branch

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /branch — isolated worktree for parallel agent sessions

Two sessions in one working dir race on HEAD (`git checkout` switches it for everyone),
uncommitted edits (leak across checkouts), and the index. Worktrees give each session its own
working files, HEAD, and index while sharing `.git`. This wraps `git worktree add` with project
conventions + a journal entry. Cost: one directory, ~zero git overhead.

## Argument shapes

```
/branch <task-slug> [--from <base-branch>] [--description "<text>"] [--reuse]
/branch list
/branch done <task-slug> [--force]
/branch update [--working-on "..."] [--state <state>] [--next "..."] [--blocked-by "..."] [--asks "..."] [--dont-touch "..."] [--slug <slug>]
/branch coord <message>
/branch coord clear <slug>
```

Parse the first positional arg and dispatch: `list`→list mode, `done`→done mode, `update`→update mode (heartbeat current entry), `coord`→coord mode (manage `## Coordination`), anything else→create mode (treat the arg as a task slug).

---

## Mode: create (default)

### 1. Resolve repo info

```bash
REPO_ROOT=$(git rev-parse --show-toplevel)
REPO_NAME=$(basename "$REPO_ROOT")
CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
# The journal lives OUT of the tracked tree, shared across all worktrees of this repo:
COORD_DIR=$(bash ~/.claude/coordination/resolve-coord-dir.sh)   # → ~/.claude/coordination/<repo>
JOURNAL="$COORD_DIR/journal.md"
```

If `git rev-parse` fails, tell the user they're not in a git repo and stop.
Read the full skill on GitHub

Details

Skill name
branch
Path
skills/branch/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Branch skill do?

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

How do I install the Branch skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill branch. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Branch popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Brag

37

iamneilroberts/claude-skills

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

Writing & Content

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

Codex

37

iamneilroberts/claude-skills

Delegate a task or question to the OpenAI Codex CLI running as an isolated subagent, then relay its answer. Use when the user invokes /codex <prompt>, says "ask codex", "have codex look at / do X", or wants a second independent model to investigate a question or make a self-contained edit. Read-only by default; /codex --write lets Codex edit the working tree. Distinct from /codex-review, which is the structured JSON review gate — /codex is a general-purpose Codex delegate.

Software Development

Curate

37

iamneilroberts/claude-skills

Verify a session's or handoff's factual claims against ground truth before trusting them. Dispatches the read-only `curator` subagent to check claims against git, files, and read-only environment checks, plus the repo's invariants doc if any, and returns a confabulation report for human spot-check. Use at pass boundaries — resuming from a handoff, before a deploy, or whenever a prior session's summary looks suspiciously clean. Triggers on `/curate`, "curate this", "verify these claims", "check the handoff for confabulation", "is this actually done".

Git & Code Review

Share Case

43

NeuroAIHub/awesome_cognitive_and_neuroscience_skills

One-command community case sharing — capture research context from your session and submit to GitHub Discussions

Git & Code Review

Fix Issue

37

iamneilroberts/claude-skills

Take a GitHub issue and actually resolve it end to end — read the issue, reproduce it, fix it in an isolated branch with a test, verify, and open a PR that closes the issue. The counterpart to /idea (which files issues): /idea captures, /fix-issue clears. Works off `gh` in whatever repo you're in. Triggers on `/fix-issue <number|url>`, "fix issue #N", "resolve this github issue", "pick up and fix issue N".

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.