An interactive, visual guide to Git for developers who use AI-assisted coding tools like GitHub Copilot, Cursor, and Claude Code.
GitVibes teaches Git through the lens of AI-assisted development. Instead of dry reference docs, it walks through real scenarios β "the AI just changed 10 files, what do I do?" β with cinematic section banners, interactive playgrounds, Mermaid diagrams, and step-by-step VS Code screenshots.
Every lesson opens with an original piece of banner art β all 40 of them, in curriculum order:
| Part | Topics |
|---|---|
| Introduction | What Git is, installing Git, what a repository is |
| 1. Enterprise Onboarding | Git config, authentication, cloning |
| 2. Core Safety Loop | git status β stage β commit, reviewing AI changes, .gitignore & secrets hygiene |
| 3. Branching & PRs | Branches, fetch/pull/push, pull requests |
| 4. Undo Toolkit | Restore, unstage, amend, reset, revert, force-with-lease, recovery matrix, detached HEAD, reflog rescue |
| 5. Advanced Workflows | Stash, rebase vs merge, merge conflicts, cherry-pick, rebase conflict recovery, tags & releases |
| 6. Git for AI Agents | Teaching agents Git (AGENTS.md, skills), enforcing standards with hooks, parallel agents w/ worktrees |
| 7. VS Code Cockpit | Source Control, Timeline & GitLens, 3-way merge editor |
| 8. Conclusion | The AI-first workflow, quick reference card, the Final Challenge, the forges beyond GitHub |
- Git Playground β run real Git commands in the browser (isomorphic-git), opened as a sidebar panel from anywhere on the site
- 20 hands-on exercises with live success detection β a β fires the moment the repo reaches the goal state, from the core loop to
bisect, interactive rebase, hook guardrails, worktree fleets, and a three-messes-at-once capstone - A truthful commit graph β real fork points, real merge edges, tags, remote-tracking positions, and detached-HEAD markers, redrawn after every command
undo/redo/sharein every terminal β share serializes your exact session into a link anyone can replay- Progress that persists β sections read, exercises completed, a self-assessed skill checklist, and spaced-repetition refresher nudges (all localStorage; no accounts, no backend)
- Expandable banners β click any section poster to open a full-screen lightbox
- VS Code screenshots β real UI with hover-to-expand and captions
- Vibe prompts β copy-paste AI prompts for common Git workflows
- Search β
βK/Ctrl+Kcommand palette with panic-query aliases ("oops", "undo reset --hard", "wrong branch") - Cheat sheet β quick command reference from the header, expandable into a full-screen three-column view, downloadable as a typeset PDF
- Light / dark theme, installable as a PWA, works offline after one visit
- Fully static β no backend; deploys to GitHub Pages
The playground lets you run real Git commands in the browser β no server, no sandboxed iframe. It pairs isomorphic-git (a full Git implementation in JavaScript) with LightningFS (an in-memory virtual filesystem backed by IndexedDB) so every git commit, git merge, and git stash behaves like the real thing.
Here's the merge-conflict exercise mid-session. Everything in the terminal is genuine Git: git status reporting unmerged paths, cat showing the actual <<<<<<< conflict markers isomorphic-git wrote into the file, a resolving commit with its real hash β and the moment the merge completes, the success check fires and the commit graph redraws with both branches joined by a true merge node:
flowchart TD
subgraph Browser["Browser (no backend)"]
Input["β¨οΈ User types a command\n<code>git commit -m 'fix bug'</code>"]
Parse["Parse & dispatch\n<b>commands.ts</b>"]
Engine["Run Git operation\n<b>git-engine.ts</b>"]
subgraph VFS["Virtual Filesystem (LightningFS)"]
FS["In-memory <code>/repo</code>\nfiles, staging area, .git/"]
end
subgraph GitImpl["Git Implementation (isomorphic-git)"]
Ops["init Β· add Β· commit\nmerge Β· rebase Β· stash\nbranch Β· checkout Β· β¦"]
end
Remote["Simulated origin remote\n<b>remote-state.ts</b>\n(fetch / push without network)"]
Output["Format & colorize output\nHTML-styled terminal lines"]
Graph["Build Mermaid git graph\n<b>git-graph.ts</b>"]
Terminal["π₯οΈ Terminal output"]
Diagram["π Live commit graph (SVG)"]
end
Input --> Parse
Parse --> Engine
Engine <--> FS
Engine <--> Ops
Engine <--> Remote
Engine --> Output
Engine --> Graph
Output --> Terminal
Graph --> Diagram
style Browser fill:transparent,stroke:#555,stroke-width:1px
style VFS fill:transparent,stroke:#7aa2f7,stroke-width:1px,stroke-dasharray:5
style GitImpl fill:transparent,stroke:#9ece6a,stroke-width:1px,stroke-dasharray:5
After every command, both the terminal and the commit graph update in sync β so you can see the effect of each operation instantly. Scenarios pre-seed the virtual repo with commits, branches, and working-tree changes to set up each lesson.
| Layer | Tool |
|---|---|
| Framework | SvelteKit (Svelte 5) |
| Styling | Tailwind CSS v4 |
| In-browser Git | isomorphic-git |
| Diagrams | Mermaid.js |
| Icons | Lucide |
| Testing | Playwright |
| Hosting | GitHub Pages (@sveltejs/adapter-static) |
git clone https://github.com/NeoVand/gitvibes.git
cd gitvibes
npm install
npm run devOpen http://localhost:5173.
| Command | Description |
|---|---|
npm run dev |
Start dev server |
npm run build |
Production build β build/ |
npm run preview |
Preview production build |
npm run check |
Type-check |
npm run lint |
Prettier + ESLint |
npm run test |
Vitest unit + Playwright e2e tests |
Section banner images live in static/images/ (kebab-case filenames). Image generation prompts for creating or updating posters are in docs/IMAGE_PROMPTS.md. Drop new art in as PNG and run node scripts/optimize-images.mjs to convert it to WebP, then node scripts/make-poster.mjs to refresh the banner poster above (it reads the curriculum order straight from the section components).
The downloadable cheat sheet PDF (static/gitvibes-cheatsheet.pdf) is rendered from the unlisted /cheatsheet-print route β after editing src/lib/data/cheat-sheet.ts, regenerate it with node scripts/make-cheatsheet-pdf.mjs (dev server running).
VS Code screenshots under static/images/vscode/ are from the Visual Studio Code documentation (Β© Microsoft, CC BY 3.0), vendored so the site has no runtime dependency on the docs CDN.
Pushes to main deploy automatically to GitHub Pages via .github/workflows/deploy.yml.
MIT



