Atomic Commits

Guide the user from a dirty working tree to a clean commit history where each commit is one logical change with a clear Conventional Commit message.

Critical: Match the Repo's Existing Commit Style First

Before drafting any commit message, run git log --oneline -15 to inspect the repo's existing commit style. Do this as the FIRST step, before proposing any type(scope): prefix. Repos vary widely:

1. Conventional Commits (feat:, fix(scope):, etc.) — many modern OSS projects
2. Sentence-case prose, no prefix (Clarify Genie 3 feature dictionaries, Simplify the published architecture directory) — many blog/doc/personal repos
3. Lowercase prose, no prefix
4. Always-single-line subjects vs always-with-body