conventional-commits

Format git commit messages according to the Conventional Commits specification.

11|2|Updated Feb 3, 2026

Search Tags:#git #changelog #versioning #conventional commits #code history #commits

Ready to run

npx skills add https://github.com/jackjin1997/ClawForge --skill conventional-commits-jackjin1997

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all commit messages adhere to the Conventional Commits specification, making your commit history clean, understandable, and machine-readable.

Core Features & Use Cases

Standardized Format: Enforces a consistent structure for commit types, scopes, descriptions, bodies, and footers.
Automated Tooling: Enables automated changelog generation, semantic versioning, and CI/CD pipeline integration.
Use Case: When you are about to commit changes to a Git repository, use this skill to ensure your commit message follows the feat:, fix:, or other conventional types, along with a clear description.

Quick Start

Use the conventional-commits skill to format your next commit message as a new feature.

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?▼

Standardizing commit messages solves the problem of unreadable git history by enforcing a consistent structure for commit types, scopes, descriptions, and bodies. This makes your code history understandable and enables automated tooling for semantic versioning.

What is the best way to structure a conventional commit for semantic versioning?▼

You can use this skill to format any git commit message by applying conventional types such as feat, fix, docs, style, refactor, perf, test, build, ci, chore, or revert. It applies to all standard commits and pull request merge commits.

Why do I need conventional commits for my CI/CD pipeline integration?▼

You need conventional commits for your CI/CD pipeline integration because they provide a machine-readable commit history that enables automated changelog generation and semantic versioning. This standardization ensures automated tooling can accurately parse and react to code changes.

Does the conventional commits format support optional scopes and bodies for clarity?▼

Yes, the conventional commits format supports optional scopes and bodies for clarity. Alongside standard commit types like feat or fix, you can include a scope to specify the affected module and a body for detailed context.