git-workflow

Atomic commits contain exactly one logical change describable in a single sentence. Separate refactoring from feature work, commit failing tests before implementations, and never mix documentation with code changes in the same commit.

The format is a type prefix followed by a description, such as 'feat: add login endpoint'. Valid types are feat, fix, docs, refactor, test, and chore, with an optional body explaining why the change was made.

Run cargo test to confirm all tests pass, cargo clippy to ensure no warnings, and cargo fmt --check to verify formatting. Then review the staged diff with git diff --cached to confirm every line matches the commit message.

Avoid the --git auto-commit flag for multi-step tasks, since it commits everything after the session ends. Use it only for self-contained tasks, and prefer manual commits between steps for complex work.

Mixing refactoring with feature changes makes reviews harder and complicates reverts when bugs appear. Commit the refactoring first, then add the feature, so each change can be understood and rolled back independently.