code-quality/atomic-commits

atomic commits Shipped

What this lens looks for

One logical change per commit; follow build-verify-commit loop (change → build → verify → commit → repeat); never stack uncommitted changes; one coherent unit of work per commit even if it touches multiple files

What its verifier checks

Each commit contains exactly one logical change; no compound diffs mixing unrelated changes; commit message describes the change in isolation. Judge from the diff and messages only — never demand evidence that a build or test run happened before the commit.