
Programming · course 15 of 105
The Everyday Git Handbook
Use Git every day without guessing: commit exactly what you mean, branch and merge, fix conflicts, undo safely and work with a remote, checked against real Git.
Not on sale yet. When sales open: $4.99 USD for this course, paid once, or every course for $9.99 USD a month. Prices
$4.99 USD, paid once. Or every course for $9.99 USD a month until you cancel; try it free for 7 days first (email only, no card, ends on its own). Tax added at checkout where it applies.
Runs in Claude (claude.ai, the Claude apps or Claude Code) with your own Claude account. A course opens there as soon as your payment goes through; nothing is shipped.
Preview
What it teaches
The Git you use every day, with no guessing: what git status --short is telling you, staging and committing exactly what you mean, branches and merges (fast-forward or merge commit), fixing a merge conflict, undoing things safely (restore, --amend, revert, the three kinds of reset, stash), and working with a remote (push, fetch, pull, ahead and behind). The AI asks 3 questions, places you, shows a short card per module, then gives you one item at a time: you say what Git will print or do after some commands, or type the command for a job, and it checks you against an answer key: everything about what Git prints or does came from running real Git.
How long
44 items. About 35-50 rounds plus a 12-item final: 2-3 sessions (estimate, not timed with a real student). The tutor gives a one-line save code at the end of each session.
The modules
4 modules, drilled one item at a time.
- M0
The words
Concept questions
- M1
Saving your work
Say what Git prints, or type the command
- M2
Branches and merging
Say what a branch or merge does, or type the command
- M3
Undoing things and working with a remote
Say what an undo, push, fetch or pull does, or type the command
Before it teaches, it asks
- 1What do you use Git for (your own code, a team at work, a class), and which commands do you already use?AI voice (ElevenLabs)
- 2notes.txt was committed earlier. You add a line to it. What does git status --short print?$ echo more >> notes.txt$ git status --short
- 3main has 1 commit. You made feature from it and committed once on feature; main hasn’t moved. On main you run git merge feature. Does it make a merge commit?
What’s exact, and what isn’t
Show
Straight from the course’s own notes.
- Produced by running Git
- Every key about what Git prints or does came from running git 2.39.5 on the item’s exact commands in a fresh scratch repository (remote items use a local bare repository as “origin”). Every accepted answer to a type-the-command question was run and does the job; every listed wrong command was run and doesn’t. 6 of the 26 listed wrong answers were also produced by running the mistake. A planted-error test (5 errors) was caught.
- Sourced
- Definitions and rules from Pro Git and the git-scm.com manual, short quotes matched word for word on the pages on 2026-10-10.
- Honest limit
- The tutor can’t run commands. Messages can differ slightly in other Git versions; the meaning taught here doesn’t. Never practise reset --hard or restore on work you care about.
- Not in it yet
- Rebase, cherry-pick, tags, reflog, GitHub pull requests, SSH keys and logins.