Git-native workflows make every change a checkpoint

A coding agent that commits every change turns git history into an audit log and makes rollback trivial. Each edit is an atomic commit (see: commit often and never ship code you cannot explain), so you review or revert at the granularity of a single prompt. A clean committed history lets you re-derive context from the repo rather than from chat transcripts.

This pattern also solves the context problem from a different angle. When every change is committed with a clear message, the git history itself becomes a readable log of what the agent did and why. You can brief the agent on recent changes by showing it the commit log rather than re-explaining the session. You can debug by asking the agent to read specific commits and explain the reasoning. The repo becomes its own context document, always up to date, never requiring a separate handoff file.