commit

Generate conventional git commit messages with type, scope, and subject.

3|Updated Jan 21, 2026

Search Tags:#automation #git #commit #validation #cli #conventional-commits

Ready to run

npx skills add https://github.com/martinacostadev/claude-react-agents --skill commit-martinacostadev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/martinacostadev/claude-react-agents/tree/main/templates/.claude/skills/shared/commit
Command: npx skills add https://github.com/martinacostadev/claude-react-agents --skill commit-martinacostadev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commits provide a standardized history, but crafting them consistently can be tedious. This skill automates creation of properly formatted commit messages from your changes.

Core Features & Use Cases

Generate type, scope, and subject following the Conventional Commits specification.
Validate subject length and formatting, with optional body and footer.
Integrate with CI or pre-commit hooks to enforce compliance.

Quick Start

Describe your changes and the tool will generate a conventional commit message.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages automatically from git changes?▼

To generate conventional commit messages automatically, you can describe your staged git changes and use this skill to produce a formatted commit message with the correct type, scope, and subject length per the Conventional Commits spec.

Can I validate commit message formatting in a CI pipeline?▼

Yes, you can validate commit message formatting in a CI pipeline by integrating this skill to enforce Conventional Commits compliance, checking type, scope, subject length, and optional body or footer structure against the specification.

What is the best way to enforce consistent conventional commits in local development?▼

The best way to enforce consistent conventional commits in local development is to integrate this skill into your pre-commit hooks, automatically generating and validating type, scope, and subject length before changes are saved to your project history.

Does this tool support generating optional body and footer sections for conventional commits?▼

Yes, this tool supports generating optional body and footer sections for conventional commits, validating their formatting alongside the required type, scope, and subject to ensure full compliance with the Conventional Commits specification.

Why do my conventional commit messages fail validation in automated workflows?▼

Your conventional commit messages may fail validation in automated workflows due to incorrect type, missing scope, or exceeding subject length limits, which this skill enforces strictly when generating and validating messages from your git changes.