git-commitlisted

# Git Commit Methodology A commit is the permanent record of a decision. A well-formed commit answers three questions: what changed, why it changed, and how to understand the change in isolation. Every commit should be correct on its own — readable without surrounding context, reversible without side effects, and meaningful in the project history. Write the prose this skill governs at a seventh-grade reading level, in STE-flavored mode — short sentences, common words, no unexplained jargon. Full methodology: `writing-prose`. Before you finalize prose this skill governs, call the Skill tool with `writing-prose` and apply its `## Self-lint` checklist. ## The 50/72 Rule ### Subject Line (50 characters) The subject line is what appears in `git log --oneline`, GitHub PR titles, and email notifications. Keep it under 50 characters. - **Imperative mood.** "Add user authentication" not "Added user authentication" or "Adds user authentication". Write as if completing the sentence "This commit will..." - **No period at the end.** The subject is a title, not a sentence. - **Capitalize the first word** (after the type prefix in Conventional Commits). - **Be specific.** "Fix bug" is not useful. "Fix null dereference in token parser" is useful. ### Body (72 characters per line) The body explains the *why*, not the *what*. The diff shows what changed. The body answers questions the diff cannot answer. - **Separate from subject with a blank line.** This is how git distinguishe