Commit Formatter

Formats Git commit messages according to the Conventional Commits specification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gonzoblasco/club-camping-lobos --skill commit-formatter-gonzoblasco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Commit Formatter
Source: https://github.com/gonzoblasco/club-camping-lobos/tree/main/.agents/skills/commit-formatter
Command: npx skills add https://github.com/gonzoblasco/club-camping-lobos --skill commit-formatter-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that every Git commit adheres to the Conventional Commits specification, enhancing readability, facilitating audits, and enabling future automation.

Core Features & Use Cases

  • Conventional Commit Formatting: Ensures commit messages follow a standardized format for better organization and understanding.
  • Customizable Types: Supports various commit types like feat, fix, refactor, etc., for different kinds of changes.
  • Automated Commit Generation: Automates the commit process in both CLI and Source Control UI environments.

Quick Start

Use the commit-formatter skill to format your next commit message following the Conventional Commits standard.

Frequently Asked Questions about Commit Formatter

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

FAQPage Schema
How do I format my Git commit messages to follow Conventional Commits?

Conventional Commits formatting standardizes your Git messages using types like feat or fix. This Skill automates that formatting process within both CLI and Source Control UI workflows to ensure message consistency.

What are Conventional Commits and when do I need them in my development workflow?

Conventional Commits is a specification standardizing Git commit messages to enhance readability and facilitate audits. You need it in software development workflows where commit message consistency is crucial for enabling future automation.

Can I use custom commit types like feat and fix when standardizing my Git messages?

Yes, you can use customizable commit types like feat, fix, and refactor when standardizing Git messages. The Skill supports various commit types to categorize different kinds of changes according to the Conventional Commits specification.

Do I need a specific Git environment to automate conventional commit generation?

Yes, standardizing commit messages requires a Git environment and knowledge of Conventional Commits. The Skill operates within this environment to automate the commit process across both CLI and Source Control UI workflows.

What is the best way to standardize Git commit messages for better code audits?

The best way to standardize Git commit messages for audits is applying the Conventional Commits specification. This ensures every commit follows a standardized format, enhancing readability and enabling future development automation.