finishing-a-development-branch

finishing-a-development-branch is a skill for Claude Code, Codex from JustMichael-80/MasterVault. It costs 44 tokens per session (1,723 once invoked), scanned A, a copy of finishing-a-development-branch, MIT.

A completion workflow for finished software changes in a Git branch, where Git is a tool for tracking code history.

In plain words
What is it for?
It helps verify tests, detect the repository setup, choose between merging, opening a pull request, or cleaning up, and carry out the selected option.
Why use it?
It prevents merging or cleaning up work before tests pass and the repository state is understood.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps verify tests, detect the repository setup, choose between merging, opening a pull request, or cleaning up, and carry out the selected option.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/justmichael-80/mastervault/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 JustMichael-80/MasterVault --skill finishing-a-development-branch
Clone the repo
git clone --depth 1 https://github.com/JustMichael-80/MasterVault

Made for: Claude Code, Codex.

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/justmichael-80/mastervault/finishing-a-development-branch/github.svg)](https://agentmods.dev/skills/justmichael-80/mastervault/finishing-a-development-branch)
Your own site
<a href="https://agentmods.dev/skills/justmichael-80/mastervault/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/justmichael-80/mastervault/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/justmichael-80/mastervault/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/justmichael-80/mastervault/finishing-a-development-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,723 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 100% 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.00044 $0.01723
Opus 5 $0.00022 $0.00861
Sonnet 5 $0.00009 $0.00345
Haiku 4.5 $0.00004 $0.00172

Measured 10d ago against content hash e6d4a812de90, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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

100% identical to finishing-a-development-branch — 0 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/superpowers/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 · 44 tokens per session scan A e6d4a812de90

Subscribe to this mod's changes

finishing-a-development-branch is a skill published in the GitHub repository JustMichael-80/MasterVault (12 stars, last pushed 28d ago), licensed MIT. It adds 44 tokens to every session and 1,723 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to finishing-a-development-branch, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

release-slice

Open-source one slice of a private system: take a component, sanitize it, run a leak-scan as a hard gate, publish to GitHub, then changelog, roadmap and tag on cadence, then the content wave. Publishing without passing the leak-scan is forbidden. Triggers: "/release-slice ", "ship the next slice".

tonydzi/second-brain-starter-kit · 76 tokens

finishing-a-development-branch

A workflow for closing a development branch after all work and tests are complete. A branch is a separate line of changes in a version-control system such as Git.

yinqd3/workbuddy-skills · 67 tokens

release-skills

A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.

JimLiu/baoyu-skills · 87 tokens

version-release

Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.

hoangsonww/Claude-Code-Agent-Monitor · 50 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…

cyanheads/obsidian-mcp-server · 104 tokens

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…

cyanheads/obsidian-mcp-server · 155 tokens