conventional-commits

f**k the pain away

23|2|Updated Jan 17, 2026

Search Tags:#git #changelog #versioning #conventional commits #commits #release

Ready to run

npx skills add https://github.com/asgarovf/locusai --skill conventional-commits-asgarovf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/asgarovf/locusai/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/asgarovf/locusai --skill conventional-commits-asgarovf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all Git commit messages adhere to the Conventional Commits specification, leading to a clean, parseable, and automated commit history.

Core Features & Use Cases

Enforces Commit Standards: Guides users to write commit messages with clear types, scopes, and descriptions.
Enables Automation: Facilitates automated changelog generation and semantic versioning based on commit types.
Use Case: When committing a new feature, use this skill to structure the commit message as feat(auth): add new login endpoint, ensuring it's correctly categorized for future release notes.

Quick Start

Use the conventional-commits skill to write a commit message for a bug fix in the API.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema

How do I format Git commit messages for automated changelog generation?▼

Git commit messages for automated changelog generation follow the Conventional Commits specification, requiring specific type categories, scopes, descriptions, and imperative mood to ensure a clean, parseable commit history.

What is the Conventional Commits specification for semantic versioning?▼

The Conventional Commits specification standardizes Git commit messages using structured types, scopes, and descriptions to facilitate automated semantic versioning and changelog generation based on commit categories.

How do I structure a Git commit message for a breaking change?▼

A Git commit message for a breaking change uses a specific commit type and an optional footer format to indicate the change, ensuring it is correctly categorized for future release notes and versioning.

Do I need any dependencies to enforce standard Git commit types?▼

No dependencies are required to enforce standard Git commit types. The specification guides writing commit messages with clear types and scopes without needing external packages.

Can I use conventional commits to automate release notes for any Git project?▼

Yes, standardizing Git commit messages with conventional commits enables automated changelog generation and semantic versioning, allowing any Git project to automate release notes by parsing commit categories.

What is the best way to write a feature commit message in Git?▼

The best way to write a feature commit message in Git is using the Conventional Commits format, structuring it as `feat(scope): description` in imperative mood to ensure correct categorization for release notes.