Git Basics
Build a GitHub repo from nothing — keys, signed commits, PR-only main, hooks and CI — by directing Claude Code and judging what it did.
10 lessons 3 phases intermediate
Get started
Signed in as your account.
why this workshop
who it's for.
Anyone who has copy-pasted git commands and wants to understand them — and wants Claude Code to do the typing from now on, safely.
what you'll build
what you walk away with.
- 01 A GitHub account, an SSH key that both authenticates and signs, and a git identity — detected if you already have them.
- 02 A private repository in your own account whose first commit shows the Verified badge.
- 03 A commit history that reads like a story: small commits, real messages, one amended before it was pushed.
- 04 A protected `main` that rejects direct pushes and accepts only squash-merged pull requests.
- 05 A `.claude/settings.json` that lets Claude read freely, asks before it writes, and refuses the destructive commands.
- 06 Two worktrees, two Claude Code sessions, two branches merged — with nothing in your main checkout disturbed.
- 07 A lefthook pre-commit hook you watched block a broken commit, and the honest way to skip it.
- 08 A GitHub Actions workflow that turns a pull request red, then green, and the branch rule that makes green mandatory.
- 09 The judgment to pick `revert`, `reset`, or `reflog` from one question: has it been pushed?
curriculum
10 lessons across 3 phases.
phase A · Identity, keys, and a repo of your own 3 lessons
- 01 Who are you to git
- 02 Keys and signatures
- 03 Your first repo
phase B · The daily loop, with Claude at the keyboard 4 lessons
- 04 Commits that tell a story
- 05 Branches and pull requests
- 06 What Claude may touch
- 07 Parallel work without stepping on yourself
phase C · Guardrails and recovery 3 lessons
- 08 Pre-commit hooks
- 09 CI that guards main
- 10 Recovering and undoing
prerequisites
what you need before you start.
- A terminal and Claude Code
- You can open a terminal, start Claude Code in a folder, and read what comes back.
- git and gh installed
- `git --version` and `gh --version` both print something. No configuration needed — the first two lessons do that, and skip what you already have.
- A browser
- Creating a GitHub account and signing `gh` in happen in a browser tab. Everything else stays in Claude Code.
- No API key
- The workshop makes no API calls of its own. The only cost is your own Claude Code session.
start
how to start.
Once Claude Code is set up, tell it “set up the git basics workshop” and it clones the project and queues the first lesson.
New here? The
getting-started guide
walks you through installing the lwc CLI and the Claude Code
plugin once — everything you need before that line works.