This is the working walkthrough for a short GitHub video series. Use the interactive guide below as the cue sheet, keep the real GitHub workflow beside it, and record the screen as you move through each episode.
Recording walkthrough
GitHub for AI builders
Use this page as the left-side cue sheet while recording. Put the real GitHub workflow on the right side, then cut the walkthrough into daily YouTube videos.
Episode 1 · 3 to 5 minGitHub for AI BuildersGitHub is not just where code lives. For AI builders, it is where ideas become reviewable work.
Show on screen
- GitHub account
- organization
- repository
- README
- issues
- pull requests
- actions
Say while showing it
- Repo equals source of truth
- Issues describe the work
- PRs create the review loop
- Checks protect the deploy path
Common mistake
Do not paste generated code into random local folders with no repo history.
Bridge to next video
Next, connect your machine so you can push and review changes safely.
Episode 2 · 3 to 5 minSSH keys and GitHub CLISSH and gh CLI make GitHub usable from your terminal without chasing personal access tokens every time.
Show on screen
- terminal
- ssh-keygen
- GitHub SSH settings
- gh auth status
- gh repo view
Say while showing it
- SSH proves this machine can push
- gh CLI proves GitHub actions from terminal work
- Do not paste secret tokens into chat or commits
Common mistake
Do not generate five random keys because the first check failed. Verify the active key and current account.
Bridge to next video
Now we can use branches and PRs instead of editing main directly.
Episode 3 · 4 to 6 minBranches, commits, and pull requestsBranches and PRs let you use AI aggressively while keeping review, rollback, and deployment sane.
Show on screen
- new branch
- small file change
- git diff
- git add
- git commit
- git push
- gh pr create
Say while showing it
- One branch per focused slice
- Diff before commit
- PR before merge
- Checks before production
Common mistake
Do not let an AI agent do a huge mixed change with no diff review.
Bridge to next video
Next, use GitHub issues to turn messy ideas into work packets AI can execute.
Episode 4 · 4 to 6 minGitHub issues as AI-ready specsA good issue is a contract: goal, constraints, files, acceptance criteria, and verification.
Show on screen
- issue title
- context
- acceptance criteria
- links
- verification checklist
- labels
Say while showing it
- Messy idea goes in, scoped task comes out
- AI needs boundaries and receipts
- Acceptance criteria tell you when to stop
Common mistake
Do not write issues that only say “make it better.” Say what better means.
Bridge to next video
Next, separate code from secrets so your app can deploy without leaking credentials.
Episode 5 · 4 to 6 minSecrets and environment variablesSecrets belong in environment stores, not commits. Your repo should know the variable names, not the private values.
Show on screen
- .env.example
- .gitignore
- GitHub secrets
- Vercel env vars
- local .env
Say while showing it
- Commit examples, not real secrets
- GitHub Actions needs CI secrets
- Vercel needs runtime/deploy secrets
- Local env stays local
Common mistake
Do not commit .env files or paste API keys into issue comments.
Bridge to next video
Next, use checks to verify the repo before anything goes live.
Episode 6 · 3 to 5 minGitHub Actions and checksChecks are the automated “does this still work?” layer before humans or deploys trust a change.
Show on screen
- Actions tab
- workflow file
- PR checks
- failed check
- fixed check
- merge button
Say while showing it
- CI catches repeatable mistakes
- Preview deploys show the actual page
- Checks do not replace visual QA, they support it
Common mistake
Do not merge just because code looks plausible. Check the result.
Bridge to next video
Wrap by inviting viewers to set up one repo, one issue, and one PR today.
Recording setup
- Put this page on the left third of the screen.
- Put GitHub, terminal, or VS Code on the right two thirds.
- Record one Loom in order, or record each episode separately.
- Say the episode marker out loud before each segment so the edit points are obvious.
- Keep each segment focused on the one workflow named in the card.
After recording
Turn the walkthrough into daily assets:
- One YouTube video per episode.
- One short blog intro per episode.
- One embedded video on this page after upload.
- One BuildLeanSaaS Discord prompt inviting people to set up their first repo.