commit-message

Generate Conventional Commits messages with enforced prefixes and 50-character subjects.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/madogiwa0124/my-agents-collection --skill commit-message-madogiwa0124
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/madogiwa0124/my-agents-collection/tree/main/skills/commit-message
Command: npx skills add https://github.com/madogiwa0124/my-agents-collection --skill commit-message-madogiwa0124

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of clear, consistent Git commit messages following the Conventional Commits standard, reducing ambiguity and review time.

Core Features & Use Cases

  • Enforces Conventional Commits prefixes (feat, fix, docs, style, refactor, test, chore) and a 50-character subject guideline.
  • Generates a subject line and a body explaining the change, ensuring a blank line between subject and body.
  • Useful for maintaining changelog entries, release notes, and contributor guidelines across software projects.

Quick Start

Describe the change you made, and the tool will generate a compliant Conventional Commit message.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I generate conventional commit messages for my git changes?

To generate conventional commit messages, describe your git changes and the tool outputs a compliant message. It enforces prefixes like feat or fix, caps the subject at 50 characters, and inserts a blank line before the body.

What is the conventional commits standard and how does it format a git commit body?

The conventional commits standard formats git messages using specific prefixes and a structured body. This tool formats the body by inserting a blank line after the subject and documenting the rationale for your changes.

Can I use this tool to write git commit messages for pull requests across software projects?

Yes, you can use this tool to write git commit messages for pull requests across software projects. It standardizes subject lines and bodies, reducing ambiguity and review time for contributors.

What is the best way to enforce a 50-character subject line limit in git commits?

The best way to enforce a 50-character subject line limit is using an automated commit message generator. This tool caps your subject at 50 characters and ensures a blank line separates it from the body.

Why does my conventional commit message need a blank line before the body?

Your conventional commit message needs a blank line before the body to separate the subject from the detailed rationale. This formatting standard ensures compatibility with automated changelog parsers and git tools.