skills.rest
smallorbit
smallorbitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

conventional-commit-message

Standardize Git commit messages with conventional types and a 72-character subject rule.

Updated Apr 17, 2026
Search Tags:#git#workflow#code-quality#lint#conventional-commits#commit-messages
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill conventional-commit-message
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commit-message
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/swarmkit/skills/conventional-commit-message
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill conventional-commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical commit messages improve history readability, tooling automation, and changelog generation by enforcing a standard format.

Core Features & Use Cases

  • Conventional types: feat, fix, chore, refactor, docs, test, style
  • Subject and body guidelines: subject limited to 72 characters with a structured body explaining motivation
  • Use Case: When committing code for a new feature, follow the conventional commits pattern to enable automatic changelog generation

Quick Start

Write a commit like feat(auth): add login flow to illustrate the conventional commits format.

Frequently Asked Questions about conventional-commit-message

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

FAQPage Schema
What are conventional commits and why use them in git workflows?▼

Conventional commits standardize git commit messages using a structured type prefix like feat or fix to improve history readability, enable tooling automation, and support automatic changelog generation across development workflows.

How do I format a conventional commit message for a new feature?▼

To format a conventional commit message, start with a type like feat, optionally add a scope in parentheses, then write a subject line under 72 characters, followed by a structured body explaining the motivation behind the change.

Which conventional commit types should I use for different git tasks?▼

Use conventional commit types including feat for new features, fix for bug fixes, chore for maintenance, refactor for code restructuring, docs for documentation, test for testing, and style for formatting changes to categorize git history.

Does the conventional commit format work for automatic changelog generation?▼

Yes, conventional commit formatting enables automatic changelog generation by parsing standardized type prefixes and structured messages to categorize features, fixes, and maintenance tasks across releases and pull requests.

What is the character limit for a conventional commit subject line?▼

The conventional commit subject line should be limited to 72 characters to maintain concise git history readability while allowing a structured body to provide additional context and motivation for the code change.

Related Skills

Explore More Software Engineering Skills→
ybbms777ybbms777
1

git-commit

Create convention-aware git commit messages with logical change grouping.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
tonombtonomb

setup-pre-commit

Configure Git pre-commit hooks with Husky and lint-staged.

Community
Intermediate
vm0-aivm0-ai
1.1k

commit

Run format, lint, type-check, and test steps before Git commits.

Official
Intermediate