We write commit messages to communicate with our future selves and teammates. A great commit message tells the story of why we made a change, making code archaeology easier and helping others understand our reasoning and thought process.
A set of rules for writing Git commit messages, which describe changes saved to a code repository. It defines message types, scopes, language, length, and a confirmation process.
Git Commit Assistant rule to enforce clean, structured, and traceable commit workflows. This rule should be applied whenever a developer attempts to stage or commit changes. It ensures that - Commits are grouped logically and use conventional commit messages tied to Jira tickets. - Feature branches are created from…
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Activate whenever editing prose-heavy files (Markdown, documentation, blog posts, READMEs, release notes, emails). Cursor port of the avoid-ai-writing skill v3.26.0. See https://github.com/conorbronsdon/avoid-ai-writing.
Gate AI done/shipped/fixed claims on ground truth from the DOS kernel (dos verify, dos commit-audit) — git ancestry and the commit's own diff, never the agent's own narration.