A tiny command-line notes tool, used as the practice repo for Unit 4, Lesson 4 (reviewing code). This repo has a branch called review-me with a small change on it — and a bug planted in that change on purpose. Your job is to have Claude review it and see whether it catches the bug.
node notes.js add <text>— add a notenode notes.js list— list all notesnode notes.js search <term>— list notes containing a termnode notes.js delete <id>— delete a note
Layout: notes.js is the entry point, lib/store.js loads, saves, and searches notes, lib/config.js holds settings, and tests/ holds the test suite (npm test).
- Make sure you have your own copy of this repo (created from the lesson on the platform).
- Clone it locally, and run
gh auth loginso Claude can open pull requests through theghCLI. - Open Claude Code in the folder.
Goal: open the review-me pull request, have Claude review it, and judge whether it caught the planted bug.
- Check the branch is there. Run
git branch -a— you should seereview-me. It came with your copy. - Open the PR. Ask Claude: "Open a pull request for the
review-mebranch." - Have Claude review it. Ask: "Review this PR — look for bugs, edge cases, and anything risky."
- Judge the review. One bug was planted on purpose. Did Claude catch it? Note what it flagged and whether it found the real problem.
- Comment. Add a one-line comment on the PR saying whether Claude caught the bug.
- Submit the pull request link.