ADR-029 — Branch Naming NNN-description

Status: Approved | Date: 2026-06-18 | Scope: All plugins

Context

Without a convention, branches accumulate with names like fix, new-feature, test2, making it impossible to track what is in review at a glance or correlate branches to PRs.

Decision

All feature branches follow the format NNN-short-description:

• NNN is a zero-padded sequential integer, per plugin, incremented for every new branch
• short-description is kebab-case English, max ~40 characters

Examples:

016-surgery-room-model
017-patient-guardian-fields
018-comms-whatsapp-integration
019-audit-consent-events
020-scheduling-calendar-v2

Branch types

Branch	Naming	Notes
Feature	NNN-description	Standard
Bug fix	NNN-fix-description	Optional fix- prefix for clarity
Hotfix on main	hotfix-AAMMDD-description	Goes directly to main via Javi

Where to find the next number

Check the highest existing branch number in the plugin:

git branch -a | grep -oE '^[0-9]+' | sort -n | tail -1

Increment by one.

Consequences

• At a glance, you see the chronological order of features developed
• PRs are naturally titled with the feature description
• No ticket system dependency (number is internal to the plugin)