What is branch-workflow?

A Git workflow for finishing a branch by preparing a pull request, choosing a merge approach, and cleaning up completed branches.

Creating pull requests, verifying tests and reviews, merging approved work, and removing safely completed branches.

It provides checks and safeguards before changes are sent for review or merged into the main codebase.

branch-workflow — Skill for Claude Code by bdfinst/agentic-dev-team

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 bdfinst/agentic-dev-team --skill branch-workflow

Clone the repo

git clone --depth 1 https://github.com/bdfinst/agentic-dev-team

Made for: Claude Code.

Or install dev-team, the plugin that ships this one along with the rest of its 98 skills, 54 agents, 4 hooks.

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/bdfinst/agentic-dev-team/branch-workflow/github.svg)](https://agentmods.dev/skills/bdfinst/agentic-dev-team/branch-workflow)

Your own site

<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/branch-workflow"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/branch-workflow/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/bdfinst/agentic-dev-team/branch-workflow"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/branch-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,349 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00069	$0.01349
Opus 5.5	$0.00028	$0.00540
Sonnet 5.5	$0.00014	$0.00270
Haiku 4.5	$0.00007	$0.00135

Measured 1mo ago against content hash 4b121bc7ecf8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

branch-workflow 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 1mo 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.

plugins/dev-team/skills/branch-workflow/SKILL.md · 90 lines

How it starts

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

Branch Workflow

Role: worker. This command performs PR creation, merge, and branch cleanup directly via git/gh commands.

Overview

The three-phase workflow ends at the Phase 3 human gate. This skill formalizes what happens after approval: PR creation, merge decision, and branch cleanup. Without this, branches linger and merge conflicts accumulate.

Constraints

Do not push to main/master directly — always use a PR
Do not force-push unless the human explicitly requests it
Do not delete branches that have unmerged work
Do not merge without a passing CI check (if CI is configured)
Do not switch branches (checkout, worktree enter) without first checking working-tree state and confirming with the human if dirty

Workflow

1. Pre-PR Checklist

Before creating the PR, verify:

All tests pass (fresh run, not cached)
/code-review passed or warnings are documented
Documentation is current (tech-writer verified in Phase 3)
Branch is rebased on latest main (resolve conflicts if needed)

2. Create the PR

Title: concise, under 70 characters, describes the change
Body: Summary (what and why), test plan, link to design doc if one exists
Labels: add relevant labels (bug, feature, refactor, docs)
Reviewers: assign based on who should review (human decides)

3. Present Options

After confirming the base branch, present exactly four choices. If this session entered a worktree via EnterWorktree for this branch, each option's cleanup step is performed with the paired ExitWorktree call below — never raw git worktree remove. If no worktree was entered via EnterWorktree (branch-workflow can also run directly in the primary checkout), the ExitWorktree steps are a no-op — skip them.

Merge locally — Integrate feature branch into base, run tests on merged result, delete feature branch, then call ExitWorktree(action="remove")
Push and create PR — Push branch and create pull request via gh pr create. Once the PR is opened, call ExitWorktree(action="keep") so the worktree persists on disk while the session's CWD bookkeeping is closed
Keep as-is — Preserve branch and worktree for later handling; call ExitWorktree(action="keep") immediately after the option is confirmed — do not leave the worktree silently "entered" for the rest of the session
Discard — Permanently delete branch and all commits. Requires the human to type "discard" to confirm. Never discard without typed confirmation. After confirmation, call ExitWorktree(action="remove", discard_changes=true)

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

1mo ago First seen · 90 lines · 69 tokens per session scan A 4b121bc7ecf8

Subscribe to this mod's changes

branch-workflow is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 1,349 once invoked, about $0.0003 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-09-03.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

branch-workflow