git-commits

Write commit messages with a concise summary line describing what changed and why, followed by a blank line and optional body details. This format improves traceability and makes your repository history readable for future reference and collaboration.

Split commits when changes address distinct concerns—such as CSS updates versus PHP logic fixes, or feature work versus refactoring. Use git diff and git status to inspect changes, then group logically related modifications into single commits for a clean, meaningful history.

When changes span multiple repositories, sequence commits by repository boundaries and logical dependencies. Inspect each repository's working tree and history with git status, git diff, and git log to determine grouping, then commit coherently within each repo to maintain traceable, isolated records.

Check git status and git diff before staging to understand your changes, decide whether to combine or split based on feature boundaries and refactoring scope, then enforce consistent commit message format. This discipline ensures a readable, navigable repository history that supports collaboration.

Yes, this commit discipline applies to any repository activity including single-file changes. Even small modifications benefit from clear, structured commit messages and deliberate staging decisions that document intent and context.

Well-structured commits with clear messages improve traceability, enable easier code review, simplify debugging via git log inspection, and make collaboration smoother. Clean commit history is a primary tool for understanding why changes were made and when regressions occurred.