# Guided Exercise: Plan a Real Commit Before You Make It

This is a paper exercise — commit to a plan before working in the Lab.

## Your task

You've made three unrelated changes to your working tree: fixed a typo in `README.md`, added a
new function to `utils.py`, and started (but not finished) an unrelated experiment in
`scratch.py` you're not ready to commit. Write out the exact sequence of commands you'd use to
end up with exactly ONE clean commit containing the README typo fix, leaving the other two files
alone.

## A worked shape to check yourself against

```
git status
git add README.md
git diff --staged
git commit -m "Fix typo in README"
git status
```

The key insight: `git add` lets you choose EXACTLY what goes into the next commit, regardless of
what else is sitting, unstaged, in your working tree — `utils.py` and `scratch.py` remain
untouched and uncommitted.

## Instructor Notes

**Facilitation:** This exercise directly tests whether Module 2's staging-area model actually
stuck — if students reach for `git add .`, that's a sign to revisit the model before the Lab.

**Approximate timing:** 8-10 minutes live discussion; 5 minutes self-paced.