Coding with AI tools

Stage 4 · Lesson 6 of 7

Committing in small, reviewed steps

Reading and reviewing AI code

your own work before each AI task, so the tool starts from a clean state. Then review its change, stage only the lines you have read with git add -p, and commit them with a clear message on their own. If the attempt is bad, git restore . throws it away in one command.

Small commits make every AI change easy to inspect with git diff, easy to revert and easy to explain later. Work on a for anything bigger than a tiny fix, so main always holds code you understood. This discipline matters more with AI, not less, because changes arrive faster than you would ever type them.

Common trapletting AI changes pile up with your own edits in one huge uncommitted mess that nobody can untangle.

A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it

Resources for this stage

Start with

  • GuideFree
    Google Engineering Practices

    Google · Intermediate

    Google's free code review guide: what reviewers look for and how to write review comments

Practise

  • After solving an exercise, read several community solutions and review them against your checklist

Keep handy

Also worth your time

Mark this stage as not done?