finishing-a-development-branch

finishing-a-development-branch is a skill for Claude Code, Codex from dr-code/tessera. It costs 44 tokens per session (838 once invoked), scanned A, original, MIT.

A workflow guide for finishing coding work on a development branch, which is a separate line of changes in a code repository. It checks tests and presents choices for merging, opening a pull request, or cleaning up.

In plain words
What is it for?
Use it after implementation is complete to verify tests, check repository state, and choose how to merge or submit the work.
Why use it?
It helps avoid ending work with unverified tests or an unclear next step for integrating the changes.

Skill for Claude CodeCodex

Part of the tessera plugin — 20 skills, 6 commands, 2 agents, 4 hooks, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/dr-code/tessera/finishing-a-development-branch
Any agent
npx skills add dr-code/tessera --skill finishing-a-development-branch
Clone the repo
git clone --depth 1 https://github.com/dr-code/tessera

Made for: Claude Code, Codex.

Or install tessera, the plugin that ships this one along with the rest of its 20 skills, 6 commands, 2 agents, 4 hooks, 1 MCP server.

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/dr-code/tessera/finishing-a-development-branch.svg)](https://agentmods.dev/skills/dr-code/tessera/finishing-a-development-branch)
Your own site
<a href="https://agentmods.dev/skills/dr-code/tessera/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/dr-code/tessera/finishing-a-development-branch.svg" alt="Measured on agentmods" 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 838 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00044 $0.00838
Opus 5 $0.00022 $0.00419
Sonnet 5 $0.00009 $0.00168
Haiku 4.5 $0.00004 $0.00084

Measured 5d ago against content hash 5f1f7b133dc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 5d 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 · 127 lines

How it starts

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

Finishing a Development Branch

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

Phase 0: Tessera Compliance Gate

If tessera MCP is configured AND a plan was registered with plan_save:

Run the tessera-verify skill BEFORE verifying tests:

1. Run tessera-verify
2. Review compliance report
   - All checklist items done?
   - All target files in git diff?
3. If gaps: complete missing implementation before proceeding

Only after tessera-verify is clean: proceed to Step 1.

Step 1: Verify Tests

# Python: uv run pytest
# Node: npm test
# Go: go test ./...

If tests fail:

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

Stop. Don't proceed to options.

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)
  • Normal repo or named-branch worktree: show 4 options
  • Detached HEAD worktree: show 3 options (no merge)

Step 3: Determine Base Branch

git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null

Step 4: Present Options

Normal repo / named-branch worktree:

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:

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

Step 5: Execute Choice

Option 1 — Merge locally:

MAIN_ROOT=$(git -C "$(git rev-parse --git-common-dir)/.." rev-parse --show-toplevel)
cd "$MAIN_ROOT"
git checkout <base-branch> && git pull && git merge <feature-branch>

Run tests on merged result. Only on success: cleanup worktree, delete branch.

Read the full file on GitHub · 127 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. 5d ago First seen · 127 lines · 44 tokens per session scan A 5f1f7b133dc4

Subscribe to this mod's changes

finishing-a-development-branch is a skill published in the GitHub repository dr-code/tessera (1 stars, last pushed 24d ago), licensed MIT. It adds 44 tokens to every session and 838 once invoked, about $0.0002 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens