Lock In Lab Intern, rank 1 of 9

INT-2choreSecond of 3 Intern tickets

Make a save point, break the page on purpose, roll it back

Takes
25 min in 3 steps
Checked
19 Nov 2026
min

Your estimate is optional. Your review compares it with how long it took; nothing is scored.

Agents are fast and confident, and sometimes confidently wrong. Before anything risky you make a save point with git, so a bad change costs you one command instead of an afternoon.

You'll commit what works, let the agent make a change you'll regret, and get back.

You'll need Git installed (git --version prints a version). The folder from INT-1, or any small project. Prices checked this month are on Tools.

Commit what works

Step 1 of 3, about 5 min

In the project folder:

git init
git add -A
git commit -m "countdown page works"

If git asks who you are, set git config --global user.name and user.email first. Any name works.

The part of a video worth watching for this step

YouTube, John Kim. Published Sep 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

the usual mistake

Committing secrets. If there's a .env file or any key in the folder, add it to .gitignore before the first commit. Removing it later doesn't remove it from history. It happened to us in INC-14, "Secrets in git, across dozens of repos".

Ask for a change you'll regret

Step 2 of 3, about 10 min

Let it do it. Look at the result and at git status and git diff --stat: git can tell you exactly which files changed and by how many lines.

Paste this to your agent
Rewrite the page in a completely different style, with animations everywhere and a new layout.

The part of a video worth watching for this step

YouTube, leerob. Published Apr 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Roll back and prove it

Step 3 of 3, about 10 min

Throw the changes away:

git restore .
git clean -n   # shows new files the agent created; run with -f to delete them

Reload the page. It should be the version you committed. Then make one small change you do like and commit it, so you finish with two commits.

The part of a video worth watching for this step

YouTube, Tech With Tim. Published Jul 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Check and ship

The whole ticket
Run:
git log --oneline && git status --short

It passes when Two or more commits listed, and git status --short prints nothing.

  • The project is a git repository with at least two commits.
  • A bad change was made and rolled back with git, not by hand.
  • git status is clean at the end.

No server checks your work in this version: you mark it, and your review says "Checked by you". Graded checks are planned for Plus.

Next: INT-3 Write the spec before you ask for code

What do you see?

Pick the closest one. Each goes to what to try first and the incident it looks like.