finishing-a-development-branch

finishing-a-development-branch is a skill for Claude Code from XRenSiu/claude-code-forge. It costs 43 tokens per session (2,085 once invoked), scanned A, original, MIT.

A checklist for closing a completed Git development branch, the separate line of work where code changes are made. It verifies tests, builds, and branch status before offering merge, pull request, keep, or discard choices.

In plain words
What is it for?
Use it after implementation and code review to run final checks, compare the branch with its base branch, and choose whether to merge locally, open a pull request, keep the branch, or discard it.
Why use it?
It prevents unfinished, untested, or uncommitted work from being merged by mistake. It also makes the final branch decision explicit.

Skill for Claude Code

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

Part of the pdforge plugin — 10 skills, 13 commands, 5 agents, 2 hooks shipped together

Good fit Use it after implementation and code review to run final checks, compare the branch with its base branch, and choose whether to merge locally, open a pull request, keep the branch, or discard it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xrensiu/claude-code-forge/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 XRenSiu/claude-code-forge --skill finishing-a-development-branch
Clone the repo
git clone --depth 1 https://github.com/XRenSiu/claude-code-forge

Made for: Claude Code.

Or install pdforge, the plugin that ships this one along with the rest of its 10 skills, 13 commands, 5 agents, 2 hooks.

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/xrensiu/claude-code-forge/finishing-a-development-branch/github.svg)](https://agentmods.dev/skills/xrensiu/claude-code-forge/finishing-a-development-branch)
Your own site
<a href="https://agentmods.dev/skills/xrensiu/claude-code-forge/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/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/xrensiu/claude-code-forge/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/finishing-a-development-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,085 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.00043 $0.02085
Opus 5.5 $0.00017 $0.00834
Sonnet 5.5 $0.00009 $0.00417
Haiku 4.5 $0.00004 $0.00209

Measured 1mo ago against content hash 0cab2846c479, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

plugins/pdforge/skills/finishing-a-development-branch/SKILL.md · 308 lines

How it starts

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

Finishing a Development Branch

Core principle: Development isn't done until the branch is properly resolved.

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

When to Use

  • All planned tasks completed
  • All tests passing
  • Code review approved
  • Ready to merge or create PR

Pre-Finish Verification

🔴 Must Verify Before Proceeding

# 1. All tests pass
npm test || yarn test || pnpm test
# Exit code must be 0

# 2. Build succeeds
npm run build || yarn build || pnpm build
# Exit code must be 0

# 3. No uncommitted changes
git status --porcelain
# Output must be empty

# 4. Branch is up to date with base
git fetch origin
git log HEAD..origin/main --oneline
# If commits exist, rebase required

If any check fails: STOP. Do not proceed until fixed.

Workflow

digraph finish_branch {
    rankdir=TB;
    
    "Verify tests pass" [shape=box];
    "Tests pass?" [shape=diamond];
    "Fix failing tests" [shape=box, style=dashed];
    "Detect base branch" [shape=box];
    "Present options" [shape=box];
    "User choice" [shape=diamond];
    "Local merge" [shape=box];
    "Create PR" [shape=box];
    "Keep branch" [shape=box];
    "Discard work" [shape=box];
    "Cleanup worktree" [shape=box];
    "Done" [shape=ellipse];
    
    "Verify tests pass" -> "Tests pass?";
    "Tests pass?" -> "Fix failing tests" [label="no"];
    "Fix failing tests" -> "Verify tests pass";
    "Tests pass?" -> "Detect base branch" [label="yes"];
    "Detect base branch" -> "Present options";
    "Present options" -> "User choice";
    "User choice" -> "Local merge" [label="merge"];
    "User choice" -> "Create PR" [label="pr"];
    "User choice" -> "Keep branch" [label="keep"];
    "User choice" -> "Discard work" [label="discard"];
    "Local merge" -> "Cleanup worktree";
    "Create PR" -> "Cleanup worktree";
    "Keep branch" -> "Done";
    "Discard work" -> "Cleanup worktree";
    "Cleanup worktree" -> "Done";
}

Read the full file on GitHub · 308 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. 1mo ago First seen · 308 lines · 43 tokens per session scan A 0cab2846c479

Subscribe to this mod's changes

finishing-a-development-branch is a skill published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 43 tokens to every session and 2,085 once invoked, about $0.0002 per session on Opus 5.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-09-05.

Related

Other skills, from other repositories

codew-release-qa-sweep

Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.

Hmbown/CodeWhale · 31 tokens

validate-release-green

Run or inspect the local Release-Green observer for an exact base or combined PR candidate, separating hard failures, advisory drift and incomplete evidence. Use for maintainer preflight; full CI acceptance remains a separate requirement.

diegosouzapw/OmniRoute · 47 tokens

verify-and-ship

Choose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.

cyrusagents/cyrus · 32 tokens

ship

Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.

plugin87/ux-ui-agent-skills · 34 tokens

ship-workflow

Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…

Mathews-Tom/armory · 158 tokens

AI Release Guardian

Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.

PramodDutta/qaskills · 54 tokens