CLASS 07 / INTRO TO VIBE CODING
Git Save Points
Give your project a memory.
Your project is more than its latest version. Git records checkpoints so you can see what changed, and GitHub can hold a remote copy of those commits. Start by watching the journey in Flight Deck.
Launch Git Flight Deck Jump to copyable prompts ↓YOUR FLIGHT PLAN
Try it. Understand it. Make it yours.
- 01
Predict, then try it
Open Git Flight Deck. Stage the files, name a checkpoint, and record a commit. Before pushing, predict whether Drew can see it on GitHub. Then test your prediction.
- 02
Change one thing
Push the first checkpoint. Change the Studio theme, stage it, and make another commit with a name that explains your change. Inspect both checkpoints to compare their snapshots.
- 03
Bring it back to your project
Open your existing Project Studio folder in VS Code and your local coding agent. Copy one prompt at a time below: inspect, commit, then push to your own GitHub repository. Verify the same commit in your browser, then make one small improvement and repeat.
COPY ONE PROMPT AT A TIME
From the handout to your coding agent.
Open the correct project folder in your local coding agent first. Read each prompt and replace any bracketed words before sending.
PROMPT 1 — FIND AND INSPECT MY PROJECT
Work in my existing local Project Studio folder. Do not edit files yet. Show the actual project path, read package.json, and name two real source files. Check Git and gh. Inspect the Git root, status, recent commits, remotes, and ignore rules if present. Do not expose credentials. Stop if this folder is inside an unrelated repository. Explain what is already set up and what is missing. If local file access or a command is blocked, show the exact problem and stop for Drew. Do not change sandbox settings or switch to a cloud session.
PROMPT 2 — RECORD A LOCAL CHECKPOINT
Preserve this Project Studio and its data. Reuse its Git repository, or initialize one here only if no repository exists. Keep dependencies, .wrangler, .build-check, .env files, and .dev.vars files out of Git. If secrets are already tracked, stop for Drew. If author settings are missing, ask for my chosen author display name and GitHub-provided no-reply email, and set them only for this repository. Show the source files and staged summary for my review before committing. After I approve, record a clearly named checkpoint, then show its short hash, message, and status. Do not push, reset, or discard work.
PROMPT 3 — SEND MY CHECKPOINT TO GITHUB
Help push this Project Studio to my GitHub account. Check authentication without showing tokens. If login is needed, guide me through gh browser sign-in; I enter credentials only in the browser. Inspect any existing remote and confirm its owner and repository with me. Reuse the intended remote without overwriting it. If none exists, ask for a repository name and create a private repository in my account. Push the current branch and set its upstream if needed. Never force push or rewrite history. If the remote has unexpected work, stop for Drew. Show the repository URL and verify that the latest remote commit matches my local hash and message.
READY TO GO FURTHER?
A little stretch.
Stage a theme change, then edit the theme again before committing. Which version did Git record? Try Undo latest local commit before pushing and investigate what stays in the working files.
KEEP THESE HANDY