branch-finish

branch-finish is a command for Claude Code from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 11 tokens per session (1,147 once invoked), scanned A, original, MIT.

A Git command for completing a development branch according to configured branch-flow rules. A branch is a separate line of code changes, and finishing it means merging those changes into the required target branch or branches.

In plain words
What is it for?
Use it to finish the current branch or a named feature, bug-fix, or hot-fix branch after checks such as a clean working directory and passing tests.
Why use it?
It gathers the usual checks and merge steps into one workflow, reducing the chance of merging an unfinished or outdated branch. It can also handle branch types that must merge into more than one target.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the github-workflows plugin — 8 skills, 9 commands, 4 agents shipped together

Good fit Use it to finish the current branch or a named feature, bug-fix, or hot-fix branch after checks such as a clean working directory and passing tests.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-finish
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.

Clone the repo
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations

Made for: Claude Code.

Or install github-workflows, the plugin that ships this one along with the rest of its 8 skills, 9 commands, 4 agents.

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 branch-finish

README.md
[![agentmods](https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-finish/github.svg)](https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-finish)
Your own site
<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-finish"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-finish/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 branch-finish

Your own site · 80×15
<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-finish"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-finish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,147 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 original No closer match found 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.00011 $0.01147
Opus 5 $0.00005 $0.00574
Sonnet 5 $0.00002 $0.00229
Haiku 4.5 $0.00001 $0.00115

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

Security

Grade A, and why

branch-finish 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 9d 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.

github-workflows/commands/branch-finish.md · 202 lines

How it starts

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

Branch Finish

Complete a branch by merging it to the appropriate target(s) following the configured flow.

Usage

/branch-finish                           # Finish current branch
/branch-finish feature/auth              # Finish specific branch

Arguments

  • First argument (optional): Branch name to finish
    • If omitted, finishes the current branch
    • Must be a valid flow branch (feature/, bugfix/, etc.)

Workflow

When this command is invoked:

  1. Identify branch: Determine which branch to finish (current or specified)

  2. Validate branch type: Ensure it's a recognized flow branch

  3. Load configuration: Get flow rules for this branch type

  4. Invoke managing-branches skill: Get branching expertise

  5. Check preconditions:

    • Working directory is clean
    • Branch is up to date
    • All tests pass (if CI integration)
  6. Determine targets: Get merge target(s) from flow config

    • Single target: feature → develop
    • Multiple targets: hotfix → main AND develop
  7. Execute merges: For each target branch:

    • Switch to target
    • Pull latest from origin
    • Merge the branch (with or without squash per config)
    • Push to origin
  8. Create tag (if configured): For releases/hotfixes

  9. Clean up:

    • Delete local branch
    • Delete remote branch
    • Remove worktree if exists
  10. Update tracking:

    • Close linked issues (via commit message)
    • Update project board

Examples

Finish current feature branch:

/branch-finish

# Merges to develop, deletes branch

Finish specific branch:

/branch-finish feature/issue-42-auth

# Merges to develop, deletes branch

Finish hotfix (multiple targets):

/branch-finish hotfix/security-patch

# Merges to main AND develop
# Creates tag v1.0.1
# Deletes branch

Finish release:

/branch-finish release/2.0.0

# Merges to main AND develop
# Creates tag v2.0.0
# Deletes branch

Output Example

Read the full file on GitHub · 202 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. 9d ago First seen · 202 lines · 11 tokens per session scan A 664e1abcbb0e

Subscribe to this mod's changes

branch-finish is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 1,147 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.