What is branch-strategy-advisor?

A guide that recommends how a team should organize Git branches, based on team size, deployment frequency, release style, and development constraints.

Use it to compare GitHub Flow, Gitflow, trunk-based development, and other branching approaches, then plan branch naming and lifetimes.

It helps teams choose a workflow that fits how they release software instead of adopting a branch model that creates unnecessary coordination and merging work.

branch-strategy-advisor — Skill for Claude Code by armanzeroeight

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 armanzeroeight/fastagent-plugins --skill branch-strategy-advisor

Clone the repo

git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

Made for: Claude Code.

Or install git-workflow-toolkit, the plugin that ships this one along with the rest of its 2 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/branch-strategy-advisor/github.svg)](https://agentmods.dev/skills/armanzeroeight/fastagent-plugins/branch-strategy-advisor)

Your own site

<a href="https://agentmods.dev/skills/armanzeroeight/fastagent-plugins/branch-strategy-advisor"><img src="https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/branch-strategy-advisor/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/armanzeroeight/fastagent-plugins/branch-strategy-advisor"><img src="https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/branch-strategy-advisor.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,905 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.01905
Opus 5.5	$0.00016	$0.00762
Sonnet 5.5	$0.00008	$0.00381
Haiku 4.5	$0.00004	$0.00191

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

Security

Grade A, and why

branch-strategy-advisor 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/git-workflow-toolkit/skills/branch-strategy-advisor/SKILL.md · 332 lines

How it starts

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

Branch Strategy Advisor

Recommend optimal branching strategies for your project.

Quick Start

Choose strategy based on team and deployment:

Small team + continuous deployment → GitHub Flow
Large team + scheduled releases → Gitflow
Fast iteration + feature flags → Trunk-Based Development

Instructions

Step 1: Assess Project Context

Team Size:

Small (1-5 developers)
Medium (6-20 developers)
Large (20+ developers)

Deployment Frequency:

Continuous (multiple times per day)
Daily
Weekly
Scheduled releases (monthly/quarterly)

Release Model:

Single production version
Multiple versions in production
Long-term support versions
Rolling releases

Technical Constraints:

Feature flags available?
Automated testing coverage?
CI/CD pipeline maturity?
Code review requirements?

Step 2: Select Branching Strategy

GitHub Flow - Best for:

Small to medium teams
Web applications
Continuous deployment
Simple workflow needed

Structure:

main (production)
  ├── feature/user-auth
  ├── feature/payment-integration
  └── bugfix/login-error

Workflow:

Create feature branch from main
Make changes and commit
Open pull request
Review and test
Merge to main
Deploy automatically

Pros: Simple, fast, continuous deployment Cons: Requires good CI/CD, no release staging

Gitflow - Best for:

Large teams
Scheduled releases
Multiple versions in production
Need for hotfix support

Structure:

main (production)
develop (integration)
  ├── feature/new-dashboard
  ├── feature/api-v2
  ├── release/v2.0
  └── hotfix/critical-bug

Workflow:

Feature branches from develop
Merge features to develop
Create release branch from develop
Test and fix in release branch
Merge release to main and develop
Tag release on main
Hotfixes from main, merge to main and develop

Pros: Structured, supports multiple versions, clear release process Cons: Complex, slower, more overhead

Read the full file on GitHub · 332 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 · 332 lines · 40 tokens per session scan A 17be3c2d566d

Subscribe to this mod's changes

branch-strategy-advisor is a skill published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,905 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-09-03.

Git and workflow Planning agent agents ai ai-agents automation chatbot

adk-git

Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a…

google/adk-python · 138 tokens

pipeline-conductor

Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.

kirodotdev/KiroCrew · 65 tokens

branch-strategy-advisor