skills.rest
mrleeio
mrleeioCOMMUNITY
Explore all skills by this author →
GitHub

conventional-commits

Format git commit messages according to the Conventional Commits standard.

Updated Mar 29, 2026
Search Tags:#code quality#git#developer tools#version control#workflow automation#conventional commits#commit messages
One-click install
npx skills add https://github.com/mrleeio/dotfiles --skill conventional-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/mrleeio/dotfiles/tree/main/dot_claude/skills/conventional-commits
Command: npx skills add https://github.com/mrleeio/dotfiles --skill conventional-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent or poorly formatted git commit messages can hinder code review, project history tracking, and automated release processes. This Skill ensures all commits adhere to the Conventional Commits standard, maintaining a clean and professional codebase.

Core Features & Use Cases

  • Standardized Commit Formatting: Automatically structures commit messages with appropriate types (e.g., feat, fix, docs), optional scopes, concise descriptions, and proper imperative mood.
  • No AI Attribution: Guarantees that commit messages are clean, professional, and free from any AI-generated attribution, maintaining human authorship and project integrity.
  • Breaking Change Indication: Helps correctly flag breaking changes with ! or a BREAKING CHANGE footer, crucial for semantic versioning and clear communication.
  • Use Case: When you're about to commit changes to a feature branch, activate this Skill to ensure your commit message follows the team's feat: Add user authentication standard, including proper capitalization and imperative mood, without any AI-generated tags.

Quick Start

Create a git commit for the new user authentication module. The commit type should be 'feat'.