Finishing a Development Branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

49 stars 8 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sodiumjoe/dotfiles --skill finishing-a-development-branch
Manual install
git clone --depth 1 https://github.com/sodiumjoe/dotfiles.git /tmp/dotfiles
mkdir -p ~/.claude/skills
cp -r /tmp/dotfiles/home/.agents/skills/finishing-a-development-branch ~/.claude/skills/finishing-a-development-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

# Finishing a Development Branch

## Overview

**Core principle:** Verify tests → Detect environment → Present options → Execute choice → Clean up.

**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."

## Step 1: Verify Tests

Run the project's full test suite (`npm test` / `cargo test` / `pytest` / `go test ./...`).

**If tests fail**, report the failures and stop — the menu comes after a green suite:

```
Tests failing (<N> failures). Must fix before completing:

[Show failures]
```

**If tests pass:** continue to Step 2.

## Step 2: Detect Environment

```bash
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
# Capture now, while still inside the workspace — Step 5 changes directory
# before cleanup (Step 6) needs this value
WORKTREE_PATH=$(git rev-parse --show-toplevel)
```

This determines which menu to show and how cleanup works:

| State | Menu | Cleanup |
|-------|------|---------|
| `GIT_DIR == GIT_COMMON` (normal repo) | Standard 3 options | No worktree to clean up |
| `GIT_DIR != GIT_COMMON`, named branch | Standard 3 options | Provenance-based (see Step 6) |
| `GIT_DIR != GIT_COMMON`, detached HEAD | Reduced 2 options (no merge) | Externally managed — leave in place |

## Step 3: Determine Base Branch

The base branch is whatever this work forked from — usually named in the
Read the full skill on GitHub

Details

Skill name
finishing-a-development-branch
Path
home/.agents/skills/finishing-a-development-branch/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Finishing a Development Branch skill do?

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

How do I install the Finishing a Development Branch skill?

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

Is Finishing a Development Branch popular?

It lives in sodiumjoe/dotfiles, which has 49 GitHub stars and 8 forks.

Related skills

Using Superpowers

49

sodiumjoe/dotfiles

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

OtherIn 2 lists

Executing Plans

49

sodiumjoe/dotfiles

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

AI, LLMs & Agents

Neovim Review

49

sodiumjoe/dotfiles

Use when the user invokes /neovim-review for a pull request or a local :Review session in Neovim.

Git & Code Review

PR Self Review

49

petekp/claude-code-setup

Draft explanatory author-context comments for the user's own PR or local diff. Use for self-review or reviewer context, not a formal review submission. Posting requires approval.

Git & Code Review10

Secrets Management Audit

49

mn-youssef/security-skills

Use when hunting for exposed secrets and auditing how an app you own manages them — API keys, tokens, passwords, and private keys in source, git history, binaries, logs, config, and CI; plus vaulting, rotation, and least-privilege of the secrets themselves.

Git & Code Review

PR Screenshot Comparison

49

petekp/claude-code-setup

Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.

Git & Code Review10

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