name	git-convention
description	Git branch naming, commit message format, and conventional commits conventions. Load when using git, creating commits, branches, or pull requests.

Git Convention

Use Conventional Commits format: type(scope): description
Breaking changes marked with ! require manual intervention
When commit message contains !, bash history expansion escapes it to \!. Use git commit -F <file> with a temp file instead of -m to avoid this
Review git log --oneline -100 before writing commit messages to match existing style
When a file has 2+ unrelated changes, commit them separately (use git add -p to stage individual hunks)

name	git-convention
description	Git branch naming, commit message format, and conventional commits conventions. Load when using git, creating commits, branches, or pull requests.

Use Conventional Commits format: type(scope): description
Breaking changes marked with ! require manual intervention
When commit message contains !, bash history expansion escapes it to \!. Use git commit -F <file> with a temp file instead of -m to avoid this
Review git log --oneline -100 before writing commit messages to match existing style
When a file has 2+ unrelated changes, commit them separately (use git add -p to stage individual hunks)

git-convention