commit-message

Generate Conventional Commits messages from git diffs with type and scope.

6|1|Updated Mar 30, 2026

Search Tags:#git #conventional commits #commit message #repository hygiene #software workflow #change description

Ready to run

npx skills add https://github.com/wesleyosantos91/multi-agents --skill commit-message-wesleyosantos91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/commit-message
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill commit-message-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates clear, consistent commit messages following Conventional Commits so your repository history stays readable and automation-friendly.

Core Features & Use Cases

Conventional Commits formatting: Creates <type>(<scope>): <description> messages with optional body and footer.
Change-aware guidance: Analyzes staged changes (git diff --cached) or all changes (git diff) to infer the right commit type and scope.
Workflow support: Helps you produce one commit per change, including breaking-change notes when applicable (e.g., BREAKING CHANGE:).

Quick Start

Use the commit-message skill to draft a Conventional Commit message for your staged changes.

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

To generate conventional commit messages from git diff, the skill reads staged or full diffs to identify the change type and optional scope, then formats them into `type(scope): description` with an optional body and footer.

What is the character limit for a conventional commit description?▼

The character limit for a conventional commit description is 72 characters. The generated messages enforce imperative lowercase English descriptions to ensure repository hygiene and keep history automation-friendly.

How do I format breaking changes in a conventional commit message?▼

To format breaking changes in a conventional commit message, the skill produces breaking-change metadata using the `BREAKING CHANGE:` footer notation based on the analyzed git diff to maintain clear repository history.

Can I use this for chore maintenance and documentation updates?▼

Yes, you can use this for chore maintenance and documentation updates. The skill supports committing code changes, tests, refactors, and CI maintenance by analyzing the actual diff to infer the correct commit type.

Does the commit-message skill work with unstaged changes?▼

Yes, the skill works with unstaged changes. It analyzes staged changes via `git diff --cached` or all unstaged changes via `git diff` to infer the appropriate commit type and scope for generating the message.

What is the best way to maintain repository hygiene with conventional commits?▼

The best way to maintain repository hygiene with conventional commits is generating one commit per change using `type(scope): description` formatting, which keeps history readable and automation-friendly across common repositories.