finishing-a-development-branch

finishing-a-development-branch is a skill for Claude Code, Codex from Drizzy07x/Skillquiver. It costs 55 tokens per session (2,005 once invoked), scanned A, original, MIT.

A workflow for wrapping up a completed Git development branch. It checks the project's tests, helps choose how to integrate the branch, and cleans up its worktree, a separate working directory for Git files.

In plain words
What is it for?
Use it after implementation is complete and tests pass. It helps verify the final checks, present integration choices, carry out the selected choice, and remove the finished worktree.
Why use it?
It prevents unfinished or unverified work from being merged and avoids leaving temporary worktrees behind. It also makes the final merge, pull request, keep, or discard choice explicit.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the skillquiver plugin — 24 skills shipped together

Good fit Use it after implementation is complete and tests pass. It helps verify the final checks, present integration choices, carry out the selected choice, and remove the finished worktree.

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

Made for: Claude Code, Codex.

Or install skillquiver, the plugin that ships this one along with the rest of its 24 skills.

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/drizzy07x/skillquiver/finishing-a-development-branch/github.svg)](https://agentmods.dev/skills/drizzy07x/skillquiver/finishing-a-development-branch)
Your own site
<a href="https://agentmods.dev/skills/drizzy07x/skillquiver/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/drizzy07x/skillquiver/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/drizzy07x/skillquiver/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/drizzy07x/skillquiver/finishing-a-development-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,005 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.00055 $0.02005
Opus 5 $0.00028 $0.01002
Sonnet 5 $0.00011 $0.00401
Haiku 4.5 $0.00006 $0.00200

Measured 10d ago against content hash 3dc8416c3798, 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.

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

How it starts

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

Finishing a Development Branch

Overview

Core principle: Verify tests → Detect environment → Present options → Execute choice → Clean up.

Shell commands below use Bash syntax — run them in a Bash-capable shell such as Git Bash on Windows.

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

Step 1: Verify Tests

Run the project's full test suite (npm test / cargo test / pytest / go test ./...). If the project has no test suite, verification is whatever check the project does have (build, lint, smoke run); if there is none, ask the user what should gate completion.

If tests fail, report the failures and stop — the menu comes after a green suite:

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

[Show failures]

If tests pass: continue to Step 2.

Step 2: Detect Environment

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)
# Capture now, while still inside the workspace — Step 5 changes directory
# before cleanup (Step 6) needs this value
WORKTREE_PATH=$(git rev-parse --show-toplevel)
BRANCH=$(git branch --show-current)
echo "GIT_DIR=$GIT_DIR"
echo "GIT_COMMON=$GIT_COMMON"
echo "WORKTREE_PATH=$WORKTREE_PATH"
echo "BRANCH=${BRANCH:-<detached>}"

Note the printed values — shell variables do not persist between tool calls, and Step 6 needs them.

This determines which menu to show and how cleanup works:

State Menu Cleanup
GIT_DIR == GIT_COMMON (normal repo) Standard 3 options No worktree to clean up
GIT_DIR != GIT_COMMON, named branch Standard 3 options Provenance-based (see Step 6)
GIT_DIR != GIT_COMMON, detached HEAD Reduced 2 options (no merge) Externally managed — leave in place

Step 3: Determine Base Branch

The base branch is whatever this work forked from — usually named in the plan, the conversation, or the branch's upstream. If it is not already known, ask: "This branch split from - is that correct?" Confirm before merging: merging into the wrong base is expensive to undo.

Read the full file on GitHub · 218 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 218 lines · 55 tokens per session scan A 3dc8416c3798

Subscribe to this mod's changes

finishing-a-development-branch is a skill published in the GitHub repository Drizzy07x/Skillquiver (2 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 2,005 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

delegate

Let Claude Architect route a versioned implementation spec through the trusted MCP runtime, independently review the Candidate Artifact, record a decision, and integrate only accepted bytes. Use for implementation delegation, Producer selection, or commitment-boundary review.

PyModel/claude-architect · 47 tokens

codex

Run the Codex CLI directly in the user's checkout for code analysis, refactoring, or automated editing without Claude Architect's verified delegation lifecycle.

PyModel/claude-architect · 31 tokens

commit

A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.

restarter/lets-workflow · 90 tokens

orient

Internal skill for commands. Render the shared orientation snapshot - active task, what's in flight, what's next - tracker-universal. Do not trigger on user conversation; only when a command needs the snapshot.

restarter/lets-workflow · 42 tokens

actor-fetch-personality

Internal skill for commands. Fetch and validate personality from URL or file path for Actor agent. Do not trigger on user conversation - only when commands need personality loading.

restarter/lets-workflow · 37 tokens

x-multi-llm-align

A review process in which two sub-agents examine an API, data format, event schema, or workflow from their separate implementation perspectives. The user passes documents and feedback between them over multiple rounds.

KtKID/x-dev-pipeline · 293 tokens