finishing-a-development-branch

An agent skill by obra, from obra/superpowers. Tags: api, developer-tools, web.

What it does

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

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add obra/superpowers --skill finishing-a-development-branch

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/obra/superpowers
cp -r superpowers/skills/finishing-a-development-branch ~/.claude/skills/finishing-a-development-branch

Safety box score

Grade C, moderate risk: 32 of 100 risk points, rated 2026-10-21. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This skill is for finishing a Git development branch: it runs the project test suite, then can merge, push, create a PR, or delete the branch/worktree. The main risks are repo-state changes and remote writes, including a destructive discard path that can permanently remove commits and workspace files after confirmation.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	2 (moderate)	It explicitly runs the project's full test suite (`npm test` / `cargo test` / `pytest` / `go test ./...`) and then performs git commands that act on the repository.
Network access	2 (moderate)	It can contact the remote via `git pull` and `git push -u origin <feature-branch>`, and it may create a pull request with forge tooling.
Filesystem reach	2 (moderate)	It removes owned worktrees with `git worktree remove "$WORKTREE_PATH"` and may delete files that exist only in that worktree during cleanup/discard.
Secrets & credentials	0 (none)	The skill does not ask for tokens, passwords, keychain access, `.env` files, or other secret stores.
Privilege & persistence	0 (none)	There is no sudo, global install, service registration, or shell/OS configuration change.
Instruction hijack surface	0 (none)	It does not instruct the agent to ignore higher-priority rules or follow remote instructions; instead it requires waiting for the human's choice.
Irreversible actions	3 (high)	It can merge branches, push commits, create PRs, and force-delete a branch with `git branch -D <feature-branch>` after confirmation, which materially changes repo state.
Transparency	0 (none)	The skill is plain Markdown with no binaries, decoded blobs, or unreviewable installers.

Before installing

Confirm the base branch is correct before any merge.
Read the cleanup section if you keep scratch files in worktrees.
Assume the skill will run the repo's full test command and may push to origin.
Verify you are comfortable with possible worktree removal and branch deletion.

Rated 2026-10-21 by an automated review of 1 file from the skill's repository.

Source

Repository: obra/superpowers (all skills from this repository)
Path: skills/finishing-a-development-branch/SKILL.md
Branch: main
Updated: 2026-09-19

executing-plans — Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution.
receiving-code-review — Use when receiving code review feedback, before implementing suggestions.
requesting-code-review — Use when completing tasks, implementing major features, or before merging to verify work meets requirements
systematic-debugging — Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development — Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees — Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via.