Clean commits are not about looking tidy for its own sake. They are about leaving a trail that future you can search, review, bisect, and trust.
What belongs in a commit
A good commit describes one meaningful unit of change. It may touch many files, but those files should tell one story.
git status --short
git add src/content src/pages src/styles README.md
git commit -m "Build launch-ready editorial blog"What does not belong
Temporary screenshots, local logs, dependency experiments, and unrelated cleanups usually make history harder to understand. A tidy .gitignore helps, but the real habit is checking what you are about to record.
The goal is not perfection. The goal is a history that still explains the work after the context has faded.
