atomic-commits

Atomic commits isolate single logical changes, making each commit reviewable in isolation. Reviewers see clear intent, spot issues faster, and understand why changes were made—reducing review friction and merge conflicts.

An atomic commit contains one logical change, leaves the codebase in a buildable state, and includes a meaningful message explaining the why. Each commit should be independently valuable and rollback-safe.

Break your feature into small, logical steps. Commit each step separately with a focused message—one change per commit. This isolates changes for easier review, testing, and rollback if needed.

Buildable commits ensure the version control history remains stable. If you need to revert a specific change or bisect for bugs, each commit works independently without breaking the build or tests.

Yes. Atomic commit discipline applies to any codebase using version control. The principle—one logical change, buildable state, meaningful message—works consistently across languages, frameworks, and project structures.

Atomic commits preserve individual logical changes in history for clarity and debugging. Squash commits combine multiple commits into one, flattening history. Atomic commits provide better traceability; use squash strategically when grouping related work for release.