commit

Create atomic git commits by applying a three-pass methodology: a content pass to isolate a single logical change, a standards pass to enforce conventional commit formatting, and a final review to validate atomicity and message quality.

Enforce conventional commit formatting by applying a standards pass that checks for conventional prefixes, correct capitalization, a 72-character line wrap, and the removal of trailing punctuation to ensure readable git history.

Git history becomes difficult to review when commits bundle multiple logical changes. Adopting an atomic commit policy ensures each commit represents a single improvement, allowing precise reversibility and independent review.

Structure your git workflow using a three-pass process: identify and stage a single logical change, apply conventional commit standards, and perform a final review to validate that the commit is truly atomic before finalizing.

Yes, the atomic commit workflow applies across feature development, bug fixes, and documentation updates, maintaining a coherent project history by ensuring every change is independently auditable and revertible.

The three-pass methodology requires strict discipline to isolate single logical changes, making it less suitable for rapid prototyping where bundled changes are preferred over a clean, auditable history and precise reversibility.