GitHub with the panic

A short, plain-English guide to using Git and GitHub with Claude Code, for people who aren't programmers.

The sequel to GitHub without the panic (the prequel). That one was about arriving on GitHub and not backing away. This one is about what happens next: you have a project, Claude Code is sitting in the folder, and you would like to stay in control of what it does.

Read it here: https://iteachc.github.io/github-with-panic/

Covers:

• what Claude Code is, and what you are actually approving when it asks permission
• starting a project: git init, a first commit, asking Claude to commit
• commits, good messages, and reading the diff before you say yes
• branches and pull requests (gh pr create), and gh auth login
• private vs public repos, and making a sanitised public copy of a private project
• .gitignore and secrets: never commit tokens, client files or student data
• worktrees: letting Claude work on a parallel copy
• "I panicked" recipes: amend, revert, restore, reset --soft, and the reflog
• pushing, and asking Claude to hold off until you have reviewed

Running example: a tutor and a team of content creators who use Claude Code to review practice-test slide decks. Entirely fictional.

Single HTML file, no dependencies, works offline. Copy it, change it, send it on.

MIT licensed.