commit-message-creator

Lint git commit messages against the Conventional Commits specification.

17|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/timhiebenthal/trellis-datamodel --skill commit-message-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message-creator
Source: https://github.com/timhiebenthal/trellis-datamodel/tree/main/.claude/skills/commit-message-creator
Command: npx skills add https://github.com/timhiebenthal/trellis-datamodel --skill commit-message-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize git commit messages to follow the Conventional Commits specification.

Core Features & Use Cases

  • Lints commit messages for type, scope, and description in real-time during commits or pull requests.
  • Suggests corrections and enforces formatting to align with the conventional commits schema.
  • Integrates with CI or pre-commit hooks to block non-conforming messages.

Quick Start

Provide commit messages that follow the Conventional Commits specification.

Frequently Asked Questions about commit-message-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce conventional commits formatting in git?

Conventional commits formatting is enforced by linting git messages for type, scope, and description syntax during commit creation or code reviews. It suggests corrections and blocks non-conforming messages through CI or pre-commit hooks to ensure consistency across projects.

What is the conventional commits specification for commit messages?

The conventional commits specification standardizes git commit messages using structured syntax for type, scope, and description. Linting messages against this schema ensures consistent versioning and automated formatting across projects.

Can I use commit message linting in CI or pre-commit hooks?

Yes, commit message linting integrates with CI or pre-commit hooks to block non-conforming messages. This validates type, scope, and description syntax in real-time during commits or pull requests to enforce the conventional commits schema.

How do I standardize git commit messages across multiple projects?

Standardize git commit messages across multiple projects by applying the conventional commits specification during commit creation and code reviews. Enforcing type, scope, and description syntax lints messages against a schema for consistent versioning and formatting.

Does commit message linting suggest corrections for non-conforming syntax?

Yes, commit message linting suggests corrections for non-conforming syntax to align with the conventional commits schema. It enforces formatting by validating type, scope, and description in real-time during commits or pull requests.