skills.rest
ferrarifankid04
ferrarifankid04COMMUNITY
Explore all skills by this author →
GitHub

commit-messages

Generate conventional commit messages following standard formatting rules.

Updated Aug 6, 2026
Search Tags:#git#changelog#code review#version control#conventional commits#commit messages#generate
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill commit-messages-ferrarifankid04
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-messages
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/claude-code/skills/commit-messages
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill commit-messages-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured commit messages is a common friction point in software teams, leading to unclear project history and harder code reviews. This Skill enforces the conventional commit format so every message is uniform and readable. ## Core Features & Use Cases - Conventional Commit Format: Produces messages in the type(scope): description structure with types like feat, fix, docs, style, refactor, test, and chore. - Style Enforcement: Keeps subject lines under 50 characters and uses imperative mood for clarity. - Use Case: After staging changes for a bug fix in the authentication module, ask for a commit message and receive something like "fix(auth): handle expired token refresh" with an optional body explaining the change. ## Quick Start Ask the assistant to generate a conventional commit message for your staged changes describing what was modified.

Frequently Asked Questions about commit-messages

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

FAQPage Schema
How do I write a conventional commit message?▼

Use the format type(scope): description, where type is one of feat, fix, docs, style, refactor, test, or chore. Keep the subject under 50 characters, use imperative mood like "add" instead of "added", and include a body for complex changes.

What commit types are used in conventional commits?▼

The standard types are feat for new features, fix for bug fixes, docs for documentation, style for formatting, refactor for code restructuring, test for tests, and chore for maintenance tasks.

How long should a commit message subject line be?▼

The subject line should stay under 50 characters. This keeps messages readable in git log output and on hosting platforms like GitHub, with longer explanations moved into the commit body.

When should I include a body in a commit message?▼

Include a body for complex changes that need context beyond the subject line, such as explaining why a change was made or describing side effects. Simple one-line changes typically do not need a body.

Why use imperative mood in commit messages?▼

Imperative mood ("add feature" not "added feature") matches git's own convention, as seen in messages generated by commands like git merge. It describes what applying the commit will do, keeping history consistent.

Related Skills

Explore More Software Engineering Skills→
maxmurrmaxmurr

generating-commit-messages

Generate commit messages from git diff --staged with WHAT/WHY summaries.

Community
Basic
koralliskorallis
90

changelog-generator

Generates changelogs from Git history, commit messages, and pull requests.

Community
Basic
owenlamontowenlamont
1

python-lint-format

Automate Python code linting and formatting with pre-commit hooks.

Community
Advanced
JiangAustinJiangAustin

chinese-commit-conventions

Standardize Chinese Git commit messages with commitlint, husky, and commitizen.

Community
Intermediate