Git

Commits are save points, branches are sandboxes, history is documentation. Treat them accordingly.

Commit discipline

• Commit after each successful slice. Don't accumulate work — a commit is a save point you can return to.
• One logical change per commit. A commit that refactors and adds a feature is two commits.
• Explain intent, not mechanics. Describe why the change matters, not what files were touched.

Change sizing

• ~100 lines per commit: good.
• ~300 lines: acceptable if one logical change.
• 1000+ lines: too large — split it.

Separate refactoring from feature work. Separate formatting from behavior changes.

Branch workflow