finishing-a-development-branch

finishing-a-development-branch is a skill for Claude Code, Codex from skainguyen1412/antigravity-superpowers. It costs 44 tokens per session (1,106 once invoked), scanned A, original, no licence file.

A workflow for wrapping up completed development work. It helps choose whether to merge the changes, open a pull request for review, or clean up the branch.

In plain words
What is it for?
Use it to finish a development branch, prepare a pull request, merge work, or remove an unused branch.
Why use it?
It removes uncertainty after the code is finished and tests pass. You get clear next steps instead of leaving integration decisions to guesswork.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to finish a development branch, prepare a pull request, merge work, or remove an unused branch.

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

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/skainguyen1412/antigravity-superpowers/finishing-a-development-branch/github.svg)](https://agentmods.dev/skills/skainguyen1412/antigravity-superpowers/finishing-a-development-branch)
Your own site
<a href="https://agentmods.dev/skills/skainguyen1412/antigravity-superpowers/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/skainguyen1412/antigravity-superpowers/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/skainguyen1412/antigravity-superpowers/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/skainguyen1412/antigravity-superpowers/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,106 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 unknown 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.00044 $0.01106
Opus 5 $0.00022 $0.00553
Sonnet 5 $0.00009 $0.00221
Haiku 4.5 $0.00004 $0.00111

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

templates/.agent/skills/finishing-a-development-branch/SKILL.md · 214 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 13d ago First seen · 214 lines · 44 tokens per session scan A 1cc1b234a3af

Subscribe to this mod's changes

finishing-a-development-branch is a skill published in the GitHub repository skainguyen1412/antigravity-superpowers (328 stars, last pushed 6mo ago), with no licence file. It adds 44 tokens to every session and 1,106 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-30.

Related

Other skills, from other repositories

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…

addyosmani/agent-skills · 89 tokens

comet-archive

A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.

rpamis/comet · 33 tokens

finishing-a-development-branch

A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.

jnMetaCode/superpowers-zh · 25 tokens

skillshare-changelog

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…

runkids/skillshare · 134 tokens

skillshare-release

End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…

runkids/skillshare · 87 tokens

prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.

CherryHQ/cherry-studio · 44 tokens