git-commit

Break changes into focused commits with a single purpose each. Review your own changes first to ensure each commit is self-contained, testable, and easy for reviewers to understand. This keeps your version control history clean and makes debugging simpler.

Conventional Commits is a standardized format for commit messages—like 'feat: add login validation' or 'fix: resolve timeout bug'. It provides consistent messaging across your team, makes commit history readable, and enables automated tooling for changelog generation and versioning.

Identify distinct goals within your changes—separate feature additions, bug fixes, or documentation updates. Stage and commit each goal independently using git add on specific files, then craft a focused message for each. This creates a logical sequence reviewers can follow.

Use multiple commits when your changes serve different purposes: a feature addition, a refactor, and a test update should be separate. A single commit works only if all changes work together toward one clear goal and remain reviewable as one unit.

Self-review catches accidental changes, incomplete logic, and messaging inconsistencies before review. Walking through your own commits reveals whether each change truly has a single purpose and whether your commit messages accurately describe what you've done.