Simple explanation

This is the one skill that ties everything together. You have learned how to build, plan, recover, automate, and protect. But all of those skills depend on one final habit: reviewing what Claude Code actually did before you say it is finished. That review happens by reading a diff. --- What is a diff? Diff is short for difference. A diff shows you exactly what changed between the old version of a file and the new version — line by line — in a format that is easy to scan even if you cannot read code. It looks like this: Lines in GREEN with a + at the start — these were ADDED. Lines in RED with a - at the start — these were REMOVED. Lines with no colour and no symbol — these were NOT changed. That is the entire system. Green means added. Red means removed. Everything else stayed the same. --- Reading a diff — step by step. When Claude Code finishes a task — it shows you a diff or offers to show you one. Step 1 — Look at how many lines changed. You asked for one button colour to change. If 3 lines changed — that makes sense. If 47 lines changed — something unexpected happened. Stop and ask why. Step 2 — Check the red lines first. Red lines were removed. These are the most important to review. Ask yourself: is this something I wanted removed? Or did Claude Code delete something important? Step 3 — Check the green lines. Green lines were added. Does this match what you asked for? Is there anything new here you did not request? Step 4 — Check the file names at the top. Every diff shows which file was changed. Did Claude Code change only the files you expected? If it changed a file you did not ask it to touch — ask why before accepting. Step 5 — If anything looks wrong — do not accept. Type: "Explain why you changed [file name] — I did not ask you to touch that file." Or type: "Revert this change and start again — make only the specific change I asked for." --- How to see a diff. In Claude Code — after any change — type: "Show me a diff of everything you just changed." In GitHub Desktop — every uncommitted change shows a diff automatically in the right panel. Click any changed file to see exactly what changed. --- The 30-second review habit. After every Claude Code task — before you do anything else, ask these three questions: 1. How many lines changed? Does that feel right for what I asked? 2. Any red lines I did not expect? 3. Any files changed I did not ask about? Three questions. Thirty seconds. This habit catches 90% of problems before they become problems. --- Why this lesson is last. Every lesson in this challenge taught you to build faster and smarter. This last lesson teaches you to build carefully. Speed without care creates messes that take longer to clean up than the time you saved building fast. The best non-developer builders are fast AND careful. They build quickly because they check properly — not instead of checking. You now have both.

What to do

Ask Claude Code to make three small changes to your site — one at a time. After each change — ask Claude Code to show you the diff: "Show me a diff of everything you just changed." Practice reading it using the 5-step process: lines changed, red lines, green lines, file names, anything unexpected. On the third change — ask Claude Code to change something you did NOT specify — just to practice catching it. Spot the unexpected change in the diff. Ask Claude Code to revert only that unexpected change: "Revert only the change to [file name] — I did not ask for that." You have just practised the most important quality control habit in non-developer building.

Copy-paste prompt

Show me a diff of everything you just changed. List each file that was modified, how many lines were added and removed in each, and flag anything you changed that I did not explicitly ask for.

Course note

Reading a diff does not require understanding code. You only need to check: does the number of changes match what I asked for, are any red lines unexpected, and did any files change that I did not mention? Three questions. Thirty seconds. Every time.

Key takeaway

You have completed the full NonDev Apps challenge — 21 days of foundations plus 7 bonus days of advanced skills. What you can do now: install and run Claude Code, write prompts that work first time, plan complex builds, use GitHub branches as a safety net, give Claude Code permanent memory with CLAUDE.md, create Skills and Agents, set Hooks that protect your project automatically, manage your context window, connect Claude Code to external tools with MCP, and review every change before accepting it. That is not a beginner's skill set. That is a builder's skill set. Now go build something real.