Use only when the user explicitly asks for a git branch name or naming suggestion. Goal: branch names are convention-aligned and communicate type, scope, and intent at a glance.
Suggest a git branch name that encodes type, scope, and intent with high information density and minimal redundancy.
Use <type>/<scope>/<intent> unless the user specifies another convention.
Apply these standards throughout the suggestion. Each standard is single-sourced here and referenced elsewhere by its ID.
pattern.follow — Follow the user’s convention If the user provides a naming convention, follow it. Otherwise use the default pattern.
type.minimal — Minimal accurate type
Choose the smallest type that fits the change: feat, fix, chore, refactor, docs, test, perf.
scope.primary — Primary scope Choose a scope that names the main module, product area, or capability being changed.
intent.form — Intent form Intent must be verb-first kebab-case.
signal.dense — Dense and non-redundant Avoid repeating scope terms in intent unless it adds clarity. Do not encode obvious repo context.
pattern.follow.type.minimal.scope.primary.intent.form, signal.dense.A revision is complete only if all checks pass.
pattern.follow, type.minimal, scope.primary, intent.form, signal.dense.