What is branch-naming-conventions?

A set of rules for naming Git branches and working with GitHub Flow, where developers create feature branches from one main branch and merge them through pull requests.

Use it when creating feature or bug-fix branches and managing their path from development to merge.

It keeps branch names predictable and gives the team a shared process for developing, reviewing, and merging changes.

branch-naming-conventions — Cursor rule for Cursor by duckduckgo

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.

Clone the repo

git clone --depth 1 https://github.com/duckduckgo/apple-browsers

Made for: Cursor.

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/rules/duckduckgo/apple-browsers/branch-naming-conventions/github.svg)](https://agentmods.dev/rules/duckduckgo/apple-browsers/branch-naming-conventions)

Your own site

<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/branch-naming-conventions"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/branch-naming-conventions/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/rules/duckduckgo/apple-browsers/branch-naming-conventions"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/branch-naming-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,906 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.00000	$0.01906
Opus 5	$0.00000	$0.00953
Sonnet 5	$0.00000	$0.00381
Haiku 4.5	$0.00000	$0.00191

Measured 8d ago against content hash debe01e296d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

branch-naming-conventions 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 8d 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.

.cursor/rules/branch-naming-conventions.mdc · 315 lines

How it starts

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

Branch Naming Conventions & GitHub Flow

Overview

DuckDuckGo browser development follows GitHub Flow, a streamlined branching strategy that maintains a single main branch with feature branches for development work.

Reference: GitHub Flow Documentation

Core Principles

Main Branch Strategy

Single source of truth: All development branches from main
Always deployable: main branch should always be in a deployable state
Merge via PR: All changes merged back through Pull Requests (except releases)

Branch Lifecycle

Create branch from main
Develop feature/fix on branch
Open Pull Request to main
Code review and testing
Merge to main
Delete branch immediately after merge

Branch Naming Conventions

Single Developer Features & Bugfixes

For work by a single developer:

Format:  <developer-name>/<feature-or-fix-name>

Examples:

alice/bookmark-sync
alice/fix-bookmark-sync
bob/credit-card-autofill
charlie/fix-crash-on-startup

Guidelines:

Use kebab-case (lowercase with hyphens)
Be descriptive but concise
Include "fix-" prefix for bugfixes when helpful

Multi-Developer Features

For collaborative features, use a two-stage approach:

1. Base Feature Branch

Format:  <feature-name>
Example: autofill

2. Individual Developer Branches

Format:  <feature-name>/<developer-name>/<sub-feature-name>
Example: autofill/alice/settings-list-changes

Workflow:

Create base feature branch from main
Developers create individual branches from base feature branch
Individual branches merge into base feature branch
Base feature branch merges into main

Release Branches

Release branches follow semantic versioning:

Format:  release/<version>
Example: release/0.18.5

Special Notes:

No developer name prefix
Use semantic versioning format
Exception: Release branches merge to main via local merge (not PR)
Delete immediately after merge

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

8d ago First seen · 315 lines · 0 tokens per session scan A debe01e296d9

Subscribe to this mod's changes

branch-naming-conventions is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (251 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,906 tokens. 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-01.

Git and workflow browsers duckduckgo ios macos

branch-naming-conventions