commit-writer

Conventional commit messages are generated by analyzing your staged git changes and diffs, then applying the Conventional Commits specification to produce a message with the correct type (feat, fix, docs, etc.), a concise subject line, and a descriptive body explaining what changed and why.

Yes. The Skill analyzes your repository's git history and existing conventions, then aligns generated messages with your project's established patterns for consistency across the codebase.

Clear commits follow Conventional Commits with a 50-character subject line and a body explaining the change's purpose. This Skill automates that process by extracting context from staged diffs and repository history to create atomic, meaningful messages.

The Skill generates messages for current staged changes by analyzing git status and diffs. For complex scenarios, ensure changes are logically staged as atomic commits; the message will reflect the staged content and align with Conventional Commits conventions.

Standardized, descriptive commit messages improve traceability, enable automated changelog generation, and help teams understand change intent. This Skill enforces Conventional Commits to reduce miscommunication and maintain readable history.

The Skill generates messages compliant with Conventional Commits and your repository's style conventions, ensuring consistency. Combined with repository practices, it helps teams maintain uniform, high-quality commit history.