Why does the skill reject my commit if I use capital letters in the subject?

The Grey Haven standard requires subjects to be entirely lowercase to maintain a consistent visual style and avoid enforcement errors in commitlint.

How should I reference Linear issues using this skill?

You should reference Linear issues in the footer of your commit message using the format 'Fixes GREY-123' or 'Related to GREY-123'.

Which commit types are supported?

Supported types are strictly limited to: feat, fix, docs, style, refactor, test, chore, perf, ci, build, and revert.

What is the maximum header length allowed by this skill?

This skill enforces a 100-character header limit, which is more generous than the traditional 50 or 72-character limits, allowing for clearer descriptions.

Grey Haven Commit Formatter

Name: Grey Haven Commit Formatter
Author: greyhaven-ai

bygreyhaven-ai

•

Developer Tools

Standardizes git commit messages using Grey Haven Studio's production-ready commitlint configuration.

About

This skill ensures all git commits follow the Grey Haven Studio standard, utilizing Conventional Commits with a specific 100-character header limit and strict lowercase subject requirements. It helps developers maintain a clean, machine-readable history by providing real-time guidance on commit types, scopes, and breaking changes, which is essential for automated changelog generation and professional repository maintenance across frontend and backend projects.

Key Features

Validates mandatory lowercase subject lines for visual consistency.
Provides a strictly defined list of valid commit types like feat, fix, and refactor.
15 GitHub stars
Automates the formatting of breaking changes and Linear issue references.
Enforces a 100-character header limit for more descriptive commit titles.
Offers context-aware scope suggestions for frontend, backend, and infrastructure.

Use Cases

Generating professional, lint-compliant git history for team projects.
Reviewing and correcting pull request commit messages during development.
Formatting complex commits that include breaking changes or multiple issue references.

About

Key Features

Validates mandatory lowercase subject lines for visual consistency.
Provides a strictly defined list of valid commit types like feat, fix, and refactor.
15 GitHub stars
Automates the formatting of breaking changes and Linear issue references.
Enforces a 100-character header limit for more descriptive commit titles.
Offers context-aware scope suggestions for frontend, backend, and infrastructure.

Use Cases

Generating professional, lint-compliant git history for team projects.
Reviewing and correcting pull request commit messages during development.
Formatting complex commits that include breaking changes or multiple issue references.