formatting-commit-messages

Format git commit messages according to the Conventional Commits specification.

6|2|Updated Jan 18, 2026

Search Tags:#git #workflow #commit #formatting #release-notes #conventional-commits

Ready to run

npx skills add https://github.com/WesleySmits/agent-skills --skill formatting-commit-messages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: formatting-commit-messages
Source: https://github.com/WesleySmits/agent-skills/tree/main/.agent/skills/commit-message-formatter
Command: npx skills add https://github.com/WesleySmits/agent-skills --skill formatting-commit-messages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messages promote consistency across a codebase by describing the nature of changes and enabling automated release notes. This skill helps users format their commits to the Conventional Commits specification by guiding the type, scope, and optional body formatting.

Core Features & Use Cases

Analyze staged changes to determine the appropriate type prefix (feat, fix, docs, etc.) and optional scope.
Detect breaking changes and signal them with a '!' suffix per the Conventional Commits spec.
Generate a properly formatted commit message and present it for user approval during code reviews or release preparation.

Quick Start

Ask the agent to format your next commit message according to Conventional Commits.

Frequently Asked Questions about formatting-commit-messages

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

FAQPage Schema

How do I format git commit messages to follow the Conventional Commits specification?▼

To format git commit messages for Conventional Commits, the skill analyzes staged diffs to detect change types, scope, and breaking changes, then outputs a properly formatted message. It automatically determines the appropriate type prefix like feat, fix, or docs.

What is the best way to generate consistent commit messages for automated release notes?▼

Generating consistent commit messages for automated release notes requires following the Conventional Commits specification. This skill analyzes your staged changes to produce structured messages, signaling breaking changes with a '!' suffix to enable reliable release note generation.

How do I detect breaking changes in staged git diffs before committing?▼

To detect breaking changes in staged git diffs, the skill analyzes the changes and checks for modifications that require a '!' suffix per the Conventional Commits spec. It then generates a properly formatted commit message signaling the breaking change for user approval.

Can I automatically determine the correct type prefix for conventional commits?▼

Yes, you can automatically determine the correct type prefix for conventional commits. The skill analyzes staged diffs to identify the nature of the changes and assigns the appropriate type prefix such as feat, fix, or docs, along with an optional scope.

Does this commit formatting approach work with standard git workflows?▼

Yes, this commit formatting approach works with standard git workflows. It is used during commit workflows to analyze staged changes and generate consistent conventional commit messages for features, fixes, docs, or release notes in your codebases.

Why do my conventional commit messages lack the correct scope and breaking change indicators?▼

Conventional commit messages lack correct scope and breaking change indicators when not properly analyzed. This skill evaluates staged diffs to detect the appropriate scope and appends the '!' suffix for breaking changes, ensuring the output message meets the specification.