Seven pieces so far, each useful on its own. But the real skill is running them together, in order, until landing a change stops feeling like a ritual and starts feeling routine. Let’s watch the whole thing on one real example.
The loop is the skill — branch, commit, push, propose, review, merge. Claude runs the git; you make the calls that need judgment.
The task: a bug where the contact form silently drops a message when the visitor leaves the name field blank — handleContact saves nothing and the visitor never knows — on my-site, the project you’ve been growing all course.
The full loop, start to finish
1. Branch it. (Lesson 8.4) “Make a branch for the contact-form fix.” Now you’ve got a sandbox. Whatever happens next, main — the version that’s live right now — stays untouched.
2. Fix it, then commit one idea. (Lessons 8.1, 8.2) Claude makes the fix in handleContact. You commit just that fix — not the unrelated typo you also spotted on the about page. One commit, one idea, so the history and the undo stay clean.
3. Check the message. (Lesson 8.3) Claude drafts “Reject contact messages with an empty name instead of silently dropping them.” You glance at it: true, scoped, explains the why. Good.
4. Push it. (Lesson 8.5) “Push this branch.” Your work is on GitHub now — but main still doesn’t have it. Nothing’s been proposed yet; you’ve just gotten it off your laptop.
5. Open the PR. (Lesson 8.6) “Open a pull request.” Claude writes the description summarizing the change. You read it, confirm it’s honest, and it’s now a proposal anyone reviewing my-site can see.
6. Handle the review. (Lesson 8.7) A reviewer notices the fix rejects an empty name but still lets a blank email through. “Handle that comment.” Claude adjusts, you commit and push, and the PR updates itself. You agreed the catch was right; if you hadn’t, you’d have said so in the thread.
7. Merge, and clean up. The reviewer approves. You merge the PR — and now main finally has the fix, reviewed and recorded. The branch did its job, so you delete it. Done.
Why this is the close
Look back at that flow. Not one step was clever. A branch is a sentence. A commit is a sentence. Opening a PR is a sentence. None of it would impress anyone on its own.
Together, they’re the difference between hoping a change is safe to ship and knowing it is — isolated on a branch, scoped into clean commits, proposed for review, merged on purpose. And notice the division of labor the whole way down: Claude ran every git command, but every judgment call was yours. Is this one commit or two? Is the message true? Is it ready to push? Is that reviewer right? That split — mechanics to Claude, judgment to you — is what “the Claude way” has meant all along.
What’s next
You can now land work the way real teams do — safely, visibly, with a paper trail. That closes the universal path: read, build, stay safe, take on big tasks, ship them. The last level is about making Claude yours — so it already knows your project’s commands, your conventions, and your preferences, instead of you re-explaining them in every single conversation. That’s Level 9.