finishing-a-development-branch

finishing-a-development-branch is a skill for Claude Code from smallocean43658/codex-superpowers. It costs 33 tokens per session (1,712 once invoked), scanned A, a copy of finishing-a-development-branch, MIT.

A workflow for finishing software work and deciding how to merge, create a pull request, clean up, or hand it off.

In plain words
What is it for?
Use it when implementation is complete, tests pass, or a development branch is ready for merge, pull request, cleanup, or handoff.
Why use it?
It verifies tests and checks the Git workspace before any branch-integration decision is made.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the superpowers plugin — 14 skills, 1 hook shipped together

Good fit Use it when implementation is complete, tests pass, or a development branch is ready for merge, pull request, cleanup, or handoff.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/smallocean43658/codex-superpowers/finishing-a-development-branch
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add smallocean43658/codex-superpowers --skill finishing-a-development-branch
Clone the repo
git clone --depth 1 https://github.com/smallocean43658/codex-superpowers

Made for: Claude Code.

Or install superpowers, the plugin that ships this one along with the rest of its 14 skills, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for finishing-a-development-branch

README.md
[![agentmods](https://agentmods.dev/badge/skills/smallocean43658/codex-superpowers/finishing-a-development-branch/github.svg)](https://agentmods.dev/skills/smallocean43658/codex-superpowers/finishing-a-development-branch)
Your own site
<a href="https://agentmods.dev/skills/smallocean43658/codex-superpowers/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/smallocean43658/codex-superpowers/finishing-a-development-branch/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for finishing-a-development-branch

Your own site · 80×15
<a href="https://agentmods.dev/skills/smallocean43658/codex-superpowers/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/smallocean43658/codex-superpowers/finishing-a-development-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,712 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01712
Opus 5 $0.00016 $0.00856
Sonnet 5 $0.00007 $0.00342
Haiku 4.5 $0.00003 $0.00171

Measured 10d ago against content hash f5e901e68633, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

finishing-a-development-branch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to finishing-a-development-branch — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/finishing-a-development-branch/SKILL.md · 242 lines

How it starts

The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Finishing a Development Branch

Overview

Guide completion of development work by presenting clear options and handling chosen workflow.

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."

The Process

Step 1: Verify Tests

Before presenting options, verify tests pass:

# Run project's test suite
npm test / cargo test / pytest / go test ./...

If tests fail:

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

[Show failures]

Cannot proceed with merge/PR until tests pass.

Stop. Don't proceed to Step 2.

If tests pass: Continue to Step 2.

Step 2: Detect Environment

Determine workspace state before presenting options:

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)

This determines which menu to show and how cleanup works:

State Menu Cleanup
GIT_DIR == GIT_COMMON (normal repo) Standard 4 options No worktree to clean up
GIT_DIR != GIT_COMMON, named branch Standard 4 options Provenance-based (see Step 6)
GIT_DIR != GIT_COMMON, detached HEAD Reduced 3 options (no merge) No cleanup (externally managed)

Step 3: Determine Base Branch

# Try common base branches
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null

Or ask: "This branch split from main - is that correct?"

Step 4: Present Options

Normal repo and named-branch worktree — present exactly these 4 options:

Implementation complete. What would you like to do?

1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work

Which option?

Detached HEAD — present exactly these 3 options:

Implementation complete. You're on a detached HEAD (externally managed workspace).

1. Push as new branch and create a Pull Request
2. Keep as-is (I'll handle it later)
3. Discard this work

Which option?

Read the full file on GitHub · 242 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 242 lines · 33 tokens per session scan A f5e901e68633

Subscribe to this mod's changes

finishing-a-development-branch is a skill published in the GitHub repository smallocean43658/codex-superpowers (6 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,712 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to finishing-a-development-branch, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

document-release

Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…

DollarDill/beads-superpowers · 103 tokens

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.

DollarDill/beads-superpowers · 44 tokens

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 native tools or git worktree fallback.

transparent-pegasus/herdrpowers · 36 tokens

finishing-a-development-branch

Use when implementation is complete, all tests pass, and the user needs to decide how to integrate the work - presents the integration candidates (merge locally, push and open a PR, push only, keep) and executes only the chosen one; never merges on its own.

transparent-pegasus/herdrpowers · 60 tokens

session-memory-handoff

A way to preserve the important state of a coding session across branches, worktrees, and handoffs. A handoff is a short note that tells the next person what changed, what was checked, what remains, and what could block the work.

sergeionlyart/minius_codex_lab · 78 tokens

architecture-compass-adr-authoring

Author a new or successor public Architecture Compass target-repository ADR and its local adoption in stark-ai-de/agent-skills. Use when a maintainer supplies a decision idea or rough requirements and wants generic requirements, paired Short/Long/Guide triplets, conflict reporting, release synchronization, validation…

stark-ai-de/agent-skills · 90 tokens