What is finishing-a-development-branch-codex?

A workflow for deciding how to finish development work on a Git branch, including checking tests and presenting next-step choices.

Use it to assess a branch against its base branch, then choose how to complete, merge, or clean up the work.

It helps reveal unfinished work, failing tests, or review gaps before a branch is merged or otherwise closed.

finishing-a-development-branch-codex — Skill for Claude Code by mzored

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 mzored/superpowers-cc-to-codex --skill finishing-a-development-branch-codex

Clone the repo

git clone --depth 1 https://github.com/mzored/superpowers-cc-to-codex

Made for: Claude Code.

Or install superpowers-cc-to-codex, the plugin that ships this one along with the rest of its 11 skills, 2 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mzored/superpowers-cc-to-codex/finishing-a-development-branch-codex/github.svg)](https://agentmods.dev/skills/mzored/superpowers-cc-to-codex/finishing-a-development-branch-codex)

Your own site

<a href="https://agentmods.dev/skills/mzored/superpowers-cc-to-codex/finishing-a-development-branch-codex"><img src="https://agentmods.dev/badge/skills/mzored/superpowers-cc-to-codex/finishing-a-development-branch-codex/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mzored/superpowers-cc-to-codex/finishing-a-development-branch-codex"><img src="https://agentmods.dev/badge/skills/mzored/superpowers-cc-to-codex/finishing-a-development-branch-codex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,173 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.01173
Opus 5.5	$0.00016	$0.00469
Sonnet 5.5	$0.00008	$0.00235
Haiku 4.5	$0.00004	$0.00117

Measured 2mo ago against content hash cc0c25d096c9, 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-codex 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 2mo 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-codex/SKILL.md · 183 lines

How it starts

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

Finishing a Development Branch

Keep Claude in the main thread for user interaction and git operations. Call the codex_branch_analysis MCP tool for bounded branch readiness analysis. Pass a prompt body that includes the current branch name, base branch, and what kind of finish decision is needed. Example:

{
  "tool": "codex_branch_analysis",
  "arguments": {
    "prompt": "Assess whether branch codex/agent-forwarding is ready to merge back to main. Call out failing tests, uncommitted work, or review gaps that would block a clean finish.",
    "workspaceRoot": "/absolute/path/to/your/repo"
  }
}

Overview

Guide completion of development work by presenting clear options and handling the chosen workflow.

Core principle: Verify tests -> Present options -> Execute choice -> Clean up.

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

Workflow

Step 1: Call Branch Analysis

Call the codex_branch_analysis MCP tool to assess branch state. Pass a prompt body that includes the current branch name, base branch, and what kind of finish decision is needed. Example:

{
  "tool": "codex_branch_analysis",
  "arguments": {
    "prompt": "Assess whether branch codex/agent-forwarding is ready to merge back to main. Call out failing tests, uncommitted work, or review gaps that would block a clean finish.",
    "workspaceRoot": "/absolute/path/to/your/repo"
  }
}

Step 2: Review Analysis Results

Check the readiness field:

Readiness	Action
`ready`	Proceed to Step 3
`tests_failing`	Show failures to user. Must fix before finishing. Stop here.
`uncommitted_work`	Prompt user to commit or stash first. Stop here.
`needs_review`	Suggest code review before finishing. User may override.

Read the full file on GitHub · 183 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.

prompts/branch-analysis-brief.md 547 B

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.

2mo ago First seen · 183 lines · 40 tokens per session scan A cc0c25d096c9

Subscribe to this mod's changes

finishing-a-development-branch-codex is a skill published in the GitHub repository mzored/superpowers-cc-to-codex (7 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 1,173 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-08-31.

Claude Code Git and workflow ai-coding claude-code-plugin codex mcp superpowers

finishing-a-development-branch-codex next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
finishing-a-development-branch-codexmzored/superpowers-cc-to-codex	Skill	7	6mo ago	MIT	A	40	Claude Code
workflowclaude-world/director-mode-lite	Skill	80	16d ago	MIT	A	52	Claude Code
smart-commitclaude-world/director-mode-lite	Skill	80	16d ago	MIT	A	49	Claude Code
handoff-claudeclaude-world/director-mode-lite	Skill	80	16d ago	MIT	A	51	Claude Code
document-releaseDollarDill/beads-superpowers	Skill	32	7d ago	MIT	A	103	Claude Code
finishing-a-development-branchDollarDill/beads-superpowers	Skill	32	7d ago	MIT	A	44	Claude Code
pr-contributionxobotyi/cc-foundry	Skill	23	6d ago	MIT	A	51	Claude Code