The Git Quest
Learn Git the way a senior engineer actually thinks about it — the commit graph first, syntax last — so AI becomes a force multiplier instead of a liability you can’t review.
✓ First 2 lessons free · no card needed · one plan unlocks every course
The course at a glance
Most people learn Git as a list of commands to memorise, then freeze the moment something goes sideways. The Git Quest does the opposite: it teaches the model first. A commit is a polaroid of your whole project; commits clip to their parents to form a graph; branches are just labels that slide along that graph; HEAD is the arrow pointing at where you are. Once that picture is solid, every command stops being magic and becomes a predictable move on a board you can see.
That mental model is exactly what makes AI safe to direct. When you can read the graph, you can review what an assistant proposes — a merge, a rebase, a force-push — instead of pasting it and hoping. The quest ends with a modern pull-request workflow and an AI-Git Playbook, and it is the recommended prerequisite for the Junior Web AI Engineer path.
How learning happens
Every chapter follows the same loop — taught in Phase 0 and run for the rest of the course. Two beats to learn, two beats to build. Most chapters take 30–60 minutes; the build chapter that closes each phase runs longer.
Learn
A short read plus an animated model of the idea. No syntax dumps — you learn what the thing is for.
Brief
Write the instruction in plain English. Precision of intent is the skill being trained here.
Review
Read what came back against a checklist. This is where engineers are actually made.
Tweak
Change one thing yourself, by hand, and watch it move. Ownership beats copy-paste.
What you need first
A terminal and a keyboard
No prior Git needed. If you can open a shell and type a command, you are ready — we build the mental model from zero.
Willing to draw the graph
The fastest learners sketch commits and parents by hand, then verify against real Git output. Curiosity beats memorisation here.
Junior Web AI Engineer
This quest is the version-control prerequisite for the main build path — every phase there ends in a clean commit and a self-reviewed PR.
The portfolio
Everything built in this course is real, runnable, and shareable — and it compounds into one flagship artefact.
The Commit Graph Map
Init a repo, take three polaroids, draw the parent-child graph by hand, then verify it against the real history.
A merged pull request
Branch, push to GitHub, open a PR reviewers don’t hate, pass the checks, and merge it cleanly.
Your AI-Git Playbook
A personal reference of prompt patterns and guardrails for directing AI through real Git work safely.
The capstone
The whole quest points at one shift: you stop fearing Git and start directing it — including the AI sitting next to you. The AI-Git Playbook is where the mental model becomes a repeatable working method.
The AI-Git Playbook
What AI must never do alone
The handful of Git operations — force-push, hard reset, history rewrites — that always need explicit human confirmation.
Patterns for git work
Reusable prompts that make an assistant propose one reviewable step at a time instead of a mystery diff.
Read before you run
Use the graph, log and diff to verify what AI suggests before it touches your history.
Undo anything
reflog, revert and restore mean almost nothing is truly lost — so you can move fast without fear.
Concept coverage matrix
Every major concept, where it's introduced, and where it pays off.
The skill ladder
What you can honestly say after each stage. Each claim maps to something you've built, run, and can show on a screen.
I can read a repo’s history
I sketch the commit graph and confirm it with log and diff.
I can collaborate on GitHub
A branch pushed, a PR opened, checks green, and merged.
I can get out of any mess
I recover lost work with reflog and resolve a rebase conflict.
I can direct AI through Git
A written playbook and the expert toolkit under my belt.
Time and pacing
Each chapter is a short read plus one small hands-on move — take a snapshot, draw the graph, open the PR. Most chapters land in 20–40 minutes. At a few chapters a week the whole quest is comfortably done in three to five weeks.
Steady pace
A few chapters a week, one snapshot at a time.
Typical chapter
A short read plus one hands-on Git move to try.
Access
Every phase’s starter and finished repo, kept for you.
One subscription. Every course.
The Git Quest isn't sold on its own. A single MJ Tech Institute plan unlocks it alongside every other course we've shipped — 8 today, with more added over time — at no extra cost.
Everything, included
Subscribe once and every course unlocks — this one and every future release. No per-course purchases, ever.
Cancel any time
Monthly and annual plans cancel from My account whenever you like. Your progress is always saved.
Start free first
The first 2 lessons of The Git Quest cost nothing, no card required, before you choose a plan.
Finish with the mental model, the PR workflow, and your own AI-Git Playbook
Phase 0 is free and takes about an hour. If it doesn't click, you've lost nothing.
Start the course today