grey-haven-commit-format

Standardize commit messages by applying consistent formatting rules: enforce a 100-character header limit, use lowercase type and subject, include required subject lines, and structure optional body and footer sections with proper blank lines. This Skill automates those rules to match Grey Haven Studio's commitlint configuration across your codebase.

Commitlint is a configuration-driven validator that enforces standardized commit message formats across a Git repository. Teams use it to maintain readable commit history, enable automated changelog generation, and prevent rejected commits due to formatting errors.

Yes. This Skill provides ready-to-use templates for features, bug fixes, and breaking changes that conform to Grey Haven standards. Templates follow the exact commit types and scope guidance in your repository guidelines, eliminating manual formatting.

No. This Skill automatically formats commit messages during creation and amendment to match Grey Haven's 100-character header, lowercase conventions, and required subject structure, eliminating manual corrections and rejection cycles.

Commit message rules enforced include 100-character header limit, lowercase type and subject, required subject line, optional body and footer sections separated by blank lines, and adherence to Grey Haven-specified commit types and scope definitions for both frontend and backend codebases.

This Skill integrates into your Git workflow by automatically standardizing messages during commit creation and amendment. It applies Grey Haven Studio's commitlint configuration without requiring manual intervention, preserving your existing development process.