git-commits-branches

You can enforce conventional commits and branch naming by applying a standardized type set, scope rules, and branch naming format like type/short-description. This ensures consistent messages and traceability across feature development and bug fixes.

The correct format for commits is type(scope): description, using types like feat, fix, or docs. Branch names should follow type/short-description with hyphens, such as feat/add-login or fix/nav-bug, keeping scopes lowercase and concise.

To write atomic commits, include one logical change per commit and avoid squashing unrelated fixes. You should also verify that tests and lint pass before committing, adding an optional body to explain why complex changes were made.

The workflow imposes a specific commit type set: feat, fix, docs, style, refactor, test, and chore. It focuses on standardizing messages and branch names to improve collaboration rather than supporting fully custom commit types.

Git branch names need hyphens as separators to maintain a standardized type/short-description format. Using hyphens ensures predictable, machine-readable branch naming that aligns with conventional commit types during PR reviews.

The best way to standardize git workflow is to impose commit type rules, scope naming conventions, and branch formats. Ensure tests and lint pass before committing, and maintain atomic commits to streamline pre-merge verification.