conventional-commits

Structure Git commit messages using the Conventional Commits specification.

Updated Aug 23, 2026

Search Tags:#git #changelog #developer tools #versioning #conventional commits #commits

Ready to run

npx skills add https://github.com/Ai-Whisperers/infrastructure-cost-tracker --skill conventional-commits-ai-whisperers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/Ai-Whisperers/infrastructure-cost-tracker/tree/main/openclaw-config/skills/conventional-commits
Command: npx skills add https://github.com/Ai-Whisperers/infrastructure-cost-tracker --skill conventional-commits-ai-whisperers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a standardized format for Git commit messages, making your project history clear, understandable, and automatable.

Core Features & Use Cases

Structured Commits: Guides users to write commit messages following the Conventional Commits specification.
Automated Changelogs: Enables tools to automatically generate changelogs based on commit types.
Semantic Versioning: Facilitates automated version bumping (patch, minor, major) based on commit types.
Use Case: Ensure all team members write commit messages like feat(auth): add password reset or fix(api): resolve user lookup bug, allowing automated tools to track changes and manage releases effectively.

Quick Start

Follow the Conventional Commits specification when writing your next Git commit message.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema

What are conventional commits and how do they structure Git commit messages?▼

Conventional commits standardize Git commit messages by defining specific commit types, scopes, and best practices. This structured format clarifies project history and enables automated changelog generation and semantic versioning.

How do I write a conventional commit message for features and bug fixes?▼

To write a conventional commit, use a structured format combining a type and optional scope, such as `feat(auth): add password reset` for features or `fix(api): resolve user lookup bug` for bug fixes, ensuring clear project history.

Can conventional commits automate changelog generation and semantic versioning?▼

Yes, conventional commits facilitate automated changelog generation and semantic versioning. By defining commit types like features and fixes, automated tools can track changes and automatically bump patch, minor, or major release versions.

Do I need any specific developer tools to start using conventional commits?▼

No specific developer tools are required to start using conventional commits. You simply follow the specification guidelines to structure your Git commit messages, allowing compatible automated release tools to process your project history later.

What is the best way to maintain clear project history with standardized commit messages?▼

The best way to maintain clear project history is to enforce a standardized commit message format using conventional commits. This ensures all team members write structured messages, allowing automated tools to track changes and manage releases effectively.