commit-message

Generate and validate conventional commit messages from the current git diff.

Updated May 21, 2026
One-click install
npx skills add https://github.com/shades-of-web/skills --skill commit-message-shades-of-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/shades-of-web/skills/tree/main/skills/commit-message
Command: npx skills add https://github.com/shades-of-web/skills --skill commit-message-shades-of-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a consistent and informative commit message format that adheres to conventional commit standards, improving code readability and collaboration.

Core Features & Use Cases

  • Conventional Commit Format: Generates commit messages that follow the Conventional Commits specification, including the subject line and body.
  • Subject Line Generation: Creates concise subject lines up to 72 characters in English.
  • Body Explanation: Provides a detailed English explanation of the commit changes.
  • Use Case: When you need to commit changes to your codebase and want to follow best practices for commit message clarity and standardization.

Quick Start

Generate a commit message for your changes to the 'feature/add-new-functionality' branch.

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 automatically from my git diff?

To generate conventional commit messages from your git diff, this Skill analyzes your staged changes and outputs a structured subject line up to 72 characters along with a detailed English body explaining the modifications.

What is the conventional commit format and how does it improve git history?

The conventional commit format standardizes commit messages with a structured subject and body, improving code readability and collaboration. This approach ensures a consistent and informative git history for your development workflow.

Can I use this to validate commit messages for a Git Flow branching strategy?

Yes, you can validate and generate commit messages suitable for teams practicing Git Flow or similar branching strategies. It ensures your commit history adheres to conventional commit standards, maintaining consistency across feature branches.

How do I write a conventional commit subject line that stays under 72 characters?

To write a conventional commit subject line under 72 characters, this Skill automatically parses your code changes and generates a concise English summary that adheres to the conventional commits specification.

Does this commit message generator support languages other than English?

No, this commit message generator currently supports English language only. It generates both the subject line and the detailed body explanation of your commit changes exclusively in English.

What are the limitations of using automated commit message generation for code reviews?

Automated commit message generation relies entirely on the current git diff to produce conventional commit messages. It does not provide broader code review analysis, focusing solely on summarizing staged code changes into structured English commit text.