A GitFlow-based workflow for organizing Git branches and worktrees. GitFlow is a branching approach for separating feature work and shared development.

Use it when developing in a Git repository, especially for creating ticket-named branches and date-prefixed worktrees.

It gives teams consistent branch names and separate working folders for parallel changes.

gitflow — Skill for Claude Code and Codex by speedscale

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/speedscale/speedy-template

agentmods

npx agentmods add skills/speedscale/speedy-template/gitflow

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/speedscale/speedy-template/gitflow/github.svg)](https://agentmods.dev/skills/speedscale/speedy-template/gitflow)

Your own site

<a href="https://agentmods.dev/skills/speedscale/speedy-template/gitflow"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/gitflow/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/speedscale/speedy-template/gitflow"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/gitflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 705 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.00025	$0.00705
Opus 5.5	$0.00010	$0.00282
Sonnet 5.5	$0.00005	$0.00141
Haiku 4.5	$0.00003	$0.00071

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

Security

Grade C, and why

gitflow scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf ../YYYY-MM-DD_SPD-XXXX-short-description

skills/gitflow/SKILL.md · 99 lines

How it starts

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

GitFlow Workflow

GitFlow branching strategy with git worktrees for parallel development.

Branch Naming

Feature branches: SPD-XXXX-short-description (NO feature/ prefix — branches are shared)
Worktree directories: Sibling directories with date prefix: ../YYYY-MM-DD_SPD-XXXX-short-description

Git Worktrees — Preferred Workflow

Use git worktrees for all feature development. Worktrees allow multiple branches to be checked out simultaneously in separate directories.

Directory Structure

Replace your-repo with your actual repo directory name from TOOLS.md.

code/
├── your-repo/                           # Main repository (on master)
├── 2026-02-13_SPD-1234-fix-auth/        # Worktree for SPD-1234
├── 2026-02-14_SPD-5678-add-logging/     # Worktree for SPD-5678
└── 2026-02-15_SPD-9012-refactor-api/    # Worktree for SPD-9012

Create a Worktree

# From main repository directory (path from TOOLS.md)
cd /path/to/your/repo
git checkout master && git pull origin master

# Create worktree with date-prefixed directory
git worktree add ../YYYY-MM-DD_SPD-XXXX-short-description -b SPD-XXXX-short-description
cd ../YYYY-MM-DD_SPD-XXXX-short-description

List Worktrees

git worktree list

Remove a Worktree (after merge)

rm -rf ../YYYY-MM-DD_SPD-XXXX-short-description
git worktree prune

Core Workflow

Starting a Feature

cd /path/to/your/repo  # from TOOLS.md
git checkout master
git pull origin master
git worktree add ../YYYY-MM-DD_SPD-XXXX-desc -b SPD-XXXX-desc
cd ../YYYY-MM-DD_SPD-XXXX-desc

Working on a Feature

# Make commits as you work
git add .
git commit -m "Add login validation (SPD-1234)"

# Regularly sync with master
git fetch origin master
git merge origin/master

# Push feature branch
git push -u origin SPD-XXXX-desc

Completing a Feature

For this workflow, completion means creating a GitLab MR (not merging locally). GitLab handles the merge after approval. See the glab-speedscale skill for MR creation.

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

2mo ago First seen · 99 lines · 25 tokens per session scan C ca0962ed4aa2

Subscribe to this mod's changes

gitflow is a skill published in the GitHub repository speedscale/speedy-template (5 stars, last pushed 8mo ago), licensed MIT. It adds 25 tokens to every session and 705 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow

gitflow