git-hygienelisted

# Git Hygiene History is a debugging tool. `bisect`, `blame`, and `revert` only work when commits are small, honest, and well described. And nothing torches user trust faster than an agent that ran one destructive git command it was not asked to run. Two goals, then: leave history useful, and never destroy anything without an explicit instruction. ## Committing 1. **Look before staging.** `git status` and `git diff` first, every time. Know exactly what is about to enter the commit; agents that stage blind commit debug prints, secrets, and stray files. 2. **Stage with intent.** Add specific files (or hunks). Avoid blanket add-everything commands when anything unrelated is sitting in the working tree. 3. **Atomic commits.** One logical change per commit. Structure changes separate from behavior changes (see safe-refactor). A reviewer should be able to describe any commit in one sentence. 4. **Messages: imperative summary, then the why.** Summary line around 72 characters or less, written as a command ("Add retry to webhook delivery", not "Added" or "adds"). The body explains why the change exists and any non-obvious decision; the diff already shows what. Check `git log` first and follow the repo's existing convention (conventional commits, ticket prefixes, whatever the house style is). 5. **Never commit** secrets, tokens, keys, credentials, `.env` files, large binaries, or generated artifacts. Scan the staged diff for these every single time; a committed secret is compromise