A set of Gitflow rules for organizing Git branches and merges. Git is a version-control system, and Gitflow separates production code, development work, features, releases, and urgent fixes into named branches.

Use it when creating feature, release, or hotfix branches; merging changes; writing commit messages; and tagging production releases.

It gives a team consistent branch names, merge paths, commit formats, and release practices, reducing mistakes during collaboration and deployment.

gitflow — Cursor rule by chand1012

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.

agentmods

npx agentmods add rules/chand1012/cursorrules/gitflow

Clone the repo

git clone --depth 1 https://github.com/chand1012/cursorrules

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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	$0.00015	$0.00640
Opus 5	$0.00008	$0.00320
Sonnet 5	$0.00003	$0.00128
Haiku 4.5	$0.00002	$0.00064

Measured yesterday against content hash 27a0c63595c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitflow 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 yesterday.

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.

Origin

This is a copy

100% identical to gitflow — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

practice/gitflow.mdc · 113 lines

How it starts

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

Gitflow Workflow Rules

Main Branches

main (or master)

Contains production-ready code
Never commit directly to main
Only accepts merges from:
- hotfix/* branches
- release/* branches
Must be tagged with version number after each merge

develop

Main development branch
Contains latest delivered development changes
Source branch for feature branches
Never commit directly to develop

Supporting Branches

feature/*

Branch from: develop
Merge back into: develop
Naming convention: feature/[issue-id]-descriptive-name
Example: feature/123-user-authentication
Must be up-to-date with develop before creating PR
Delete after merge

release/*

Branch from: develop
Merge back into:
- main
- develop
Naming convention: release/vX.Y.Z
Example: release/v1.2.0
Only bug fixes, documentation, and release-oriented tasks
No new features
Delete after merge

hotfix/*

Branch from: main
Merge back into:
- main
- develop
Naming convention: hotfix/vX.Y.Z
Example: hotfix/v1.2.1
Only for urgent production fixes
Delete after merge

Commit Messages

Format: type(scope): description
Types:
- feat: New feature
- fix: Bug fix
- docs: Documentation changes
- style: Formatting, missing semicolons, etc.
- refactor: Code refactoring
- test: Adding tests
- chore: Maintenance tasks

Version Control

Semantic Versioning

MAJOR version for incompatible API changes
MINOR version for backwards-compatible functionality
PATCH version for backwards-compatible bug fixes

Pull Request Rules

All changes must go through Pull Requests
Required approvals: minimum 1
CI checks must pass
No direct commits to protected branches (main, develop)
Branch must be up to date before merging
Delete branch after merge

Branch Protection Rules

main & develop

Require pull request reviews
Require status checks to pass
Require branches to be up to date
Include administrators in restrictions
No force pushes
No deletions

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

yesterday First seen · 113 lines · 15 tokens per session scan A 27a0c63595c6

Subscribe to this mod's changes

gitflow is a cursor rule published in the GitHub repository chand1012/cursorrules (13 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 640 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gitflow, differing in 5 lines, and is treated as a copy.

Git and workflow Productivity Writing and docs

gitflow