Scope Your Commits
One logical change per commit — name the files and say what changed and why.
A commit should capture one logical change, and its message should say what changed and why. When you ask Claude to stage and commit, tell it exactly which files belong together and what the change accomplishes. Vague requests like 'commit everything' bundle unrelated work into one hard-to-review, hard-to-revert commit. Naming the scope keeps history clean and each commit independently reversible.
Where you'll practice this
One Promptles scenario teaches this principle directly.
The Tangled Working Tree
You've been heads-down and your working tree now has two unrelated changes: you fixed a typo in `README.md` and you also added input validation to `src/auth/login.ts`. `git status` shows both files modified. You want to commit them as two separate, well-described commits so the…