Git Conventions

Commit messages

<type>: <description>

Type	Use for
`feat:`	New functionality
`fix:`	Bug fixes
`refactor:`	Code restructuring without changing behavior
`chore:`	Maintenance, dependencies, tooling, etc.
`docs:`	Documentation
`style:`	Formatting/style-only changes
`test:`	Tests
`perf:`	Performance improvements
`build:`	Build system/tooling changes
`ci:`	CI/CD changes

Examples:

feat: add dark mode toggle
fix: correct mobile navigation spacing
refactor: simplify SEO metadata
chore: update dependencies
docs: document accessibility testing

Branch names

Use:

<type>/<short-description>

Examples:

feat/dark-mode
fix/mobile-navigation
refactor/seo-metadata
chore/update-dependencies
docs/accessibility-guide

Keep branch names lowercase, short, and kebab-case.

Quick rule

Branch: What am I working on?

fix/mobile-navigation

Commit: What did I just do?

fix: prevent navigation from overflowing on mobile