commit-msg

Generate structured Git commit messages with conventional tags and per-file summaries.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ayazhankadessova/essential-skills --skill commit-msg-ayazhankadessova
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-msg
Source: https://github.com/ayazhankadessova/essential-skills/tree/main/plugins/essential-skills/skills/commit-msg
Command: npx skills add https://github.com/ayazhankadessova/essential-skills --skill commit-msg-ayazhankadessova

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the creation of Git commit messages, ensuring clarity, consistency, and adherence to conventional commit formats, which improves code history readability and automation.

Core Features & Use Cases

  • Structured Commit Messages: Generates messages with conventional tags (feat, fix, docs, etc.) and optional per-file summaries.
  • Tag Selection Guidance: Provides clear rules for choosing the most appropriate tag based on the commit's intent.
  • Use Case: When committing a new feature, use this skill to automatically generate a message like [feat]: Add user authentication module with a breakdown of changed files.

Quick Start

Use the commit-msg skill to generate a commit message for your staged changes.

Frequently Asked Questions about commit-msg

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

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

To generate conventional commit messages, this Skill analyzes your staged changes and outputs structured text using conventional tags like feat or fix, along with per-file change summaries to maintain a clean commit history.

What is the conventional commits format and when do I need it for version control?

The conventional commits format standardizes git commit messages using structured tags to indicate intent, such as feat for features or fix for bug fixes, improving code history readability and enabling automated version control processes.

How do I choose the right conventional commit tag for my code review changes?

Choosing the right conventional commit tag involves matching your commit intent to predefined categories like feat, fix, or docs, ensuring your code review history remains structured and easily auditable.

Can I include issue references and per-file summaries in my git commit message?

Yes, you can include optional body content with issue references and per-file change summaries in your git commit message, providing detailed context alongside the conventional commit tag header.

Does this structured commit message generator work without external developer tools?

Yes, this structured commit message generator works without external dependencies, operating independently to produce conventional commit formats directly from your provided staged change data.

What are the limitations of automating git commit message formatting?

A limitation of automating git commit message formatting is that the Skill relies on accurate change descriptions to select appropriate conventional tags, meaning ambiguous diffs may produce less precise commit history annotations.