Commit frequently and review everything before shipping

Treat commits as save points. After each small task, commit with a clear message so you can revert if the next suggestion goes sideways. Use branches or worktrees to isolate experiments. If the agent generates something convoluted, ask it to simplify before committing.

The practice of committing after each small task creates natural review boundaries (see: git-native workflows make every change a checkpoint). If something breaks, git bisect pinpoints which commit caused it. If the agent went in the wrong direction, you revert one commit rather than untangling a mess. The rule about explanation is the real safeguard: if you cannot explain what a commit does in one sentence, you do not understand it well enough to ship it. This discipline catches the gap between plausible output and genuine comprehension.