--- name: git-commit description: Generates well-structured git commit messages following conventional commit standards and best practices. Creates clear, descriptive commits with proper type prefixes (feat, fix, docs, refactor, etc.), concise subjects, and detailed bodies when needed. Use when committing code changes, creating git commits, writing commit messages, or when users mention "commit", "git commit", "commit message", "conventional commits", "changelog", or need help structuring version control messages. Ensures commits are atomic, descriptive, and follow team conventions. --- # Git Commit Generates well-structured git commit messages following conventional commit standards and best practices. ## Key Principles 1. **Be specific**: Describe exactly what changed 2. **Be consistent**: Follow conventional commit format 3. **Be atomic**: One logical change per commit 4. **Be clear**: Write for others (including future you) 5. **Be complete**: Include why and context when needed 6. **Be conventional**: Follow standard format for automation ## Standard Format ``` ():