Master GitHub by doing it
A fast path for building repo reflexes: commands, drills, reviews, automation, security.
Your progress
Track the reps that matter: modules completed, commands copied, and learning events stored in Postgres.
The fastest way to learn
Do tiny reps. Break things safely. Explain each command back in plain English before moving on.
Thesaurus
Plain words mapped to expert terms so the coach can meet you where you are.
Daily command reps
Muscle memory beats theory. Run the current module commands in a throwaway repo until they feel boring.
Gemini GitHub Coach
Ask for explanations, drills, command reviews, PR practice, issue templates, and security checks. Chat history is stored in Postgres when configured.
Modern vibe coder playbook
How fast AI-assisted builders keep projects clean enough for agents and humans to work together.
Give agents a map
Use `AGENTS.md`, `CLAUDE.md`, Cursor rules, or Copilot instructions to define commands, style, security rules, and testing expectations.
Work in small slices
One issue, one branch, one pull request. Small changes are easier to review, test, revert, and explain.
Keep context outside chat
Put architecture notes, decision logs, schemas, and runbooks in the repo so every coder and agent starts from the same facts.
Let checks guard speed
Use Actions for tests, formatting, dependency review, secret scanning, and code scanning before merging.
Security rules before uploading
GitHub is powerful because it shares code. That also means secrets and sensitive details need strict handling.
- Keep serious personal infrastructure in private repos.
- Add `.env` and local config files to `.gitignore`.
- Turn on secret scanning and push protection where available.
- Never commit API keys, passwords, tokens, or sensitive operational data.