skills.rest
pantheon-org
pantheon-orgOFFICIAL
Explore all skills by this author →
GitHub

conventional-commits

Generate Git commit messages following the Conventional Commits specification.

9|Updated Feb 21, 2026
Search Tags:#git#changelog#version control#conventional commits#commits#semantic versioning
One-click install
npx skills add https://github.com/pantheon-org/tekhne --skill conventional-commits-pantheon-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/pantheon-org/tekhne/tree/main/skills/documentation/conventional-commits
Command: npx skills add https://github.com/pantheon-org/tekhne --skill conventional-commits-pantheon-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers consistently format Git commit messages according to the Conventional Commits specification, improving project clarity and automating changelog generation.

Core Features & Use Cases

  • Commit Message Generation: Creates well-formatted commit messages with type, scope, description, body, and footers.
  • Specification Adherence: Ensures messages follow the Conventional Commits standard for better version control.
  • Use Case: When you've just fixed a bug, use this skill to generate a fix commit message, specifying the affected component and providing a clear description of the fix.

Quick Start

Use the conventional-commits skill to help write a git commit message for staged changes.

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

Format git commit messages using the Conventional Commits specification to enable automated changelog generation. Structuring messages with specific types, scopes, and descriptions ensures a clear project history that semantic versioning tools can parse automatically.

What is the Conventional Commits specification for version control?▼

The Conventional Commits specification is a standard for structuring git commit messages. It defines a syntax for commit types, scopes, descriptions, bodies, and footers, facilitating structured commit history for automated semantic versioning and changelog generation.

How do I write a git commit message when I've fixed a bug?▼

Generate a git commit message using the fix type to signal a bug fix. Specify the affected component in the scope, provide a clear description of the fix, and add footers for any breaking changes to maintain a structured commit history.

Does structuring commit messages with conventional commits support semantic versioning?▼

Structuring commit messages with conventional commits directly supports semantic versioning. By using specific commit types like fix or feat, the specification allows automated tools to determine version bumps and generate comprehensive changelogs.

What are the limitations of conventional commits for git history?▼

Conventional commits require strict adherence to the formatting specification, including types, scopes, and footers, to function correctly. If messages deviate from the standard, automated changelog generation and semantic versioning parsing will fail to recognize the changes accurately.

Related Skills

Explore More Software Engineering Skills→
ThedouglerThedougler

git-commit

Generate conventional git commit messages with automated file staging.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
74nu574nu5

git-commit

Generate conventional commit messages from diffs and stage files.

Community
Intermediate
alexismanuelalexismanuel

git-commit-helper

Generate Conventional Commits messages from Git staged diffs.

Community
Intermediate