conventional-commits

Enforce Conventional Commits v1.0.0 for automated changelogs and versioning.

Updated Jan 18, 2026

Search Tags:#automation #git #changelog #semantic-versioning #conventional-commits #commit-messages

Ready to run

npx skills add https://github.com/thoroc/artemis --skill conventional-commits-thoroc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to writing commit messages that are machine-readable, enabling automated changelogs and versioning.

Core Features & Use Cases

Guidance on the Conventional Commits v1.0.0 specification, including required structure, core and additional types.
Examples illustrating good versus bad commits, handling breaking changes, and mapping to semantic versioning.
Support for automated release tooling, changelog generation, and CI/CD workflows.

Quick Start

Draft a conventional commit message such as feat(auth): add OAuth2 login capability to demonstrate the correct format.

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 enable automated semantic versioning?▼

Conventional commits are a structured message format for Git that makes commit history machine-readable, enabling automated changelog generation and semantic versioning based on commit types like features or fixes.

How do I format a breaking change in a conventional commit message?▼

To format a breaking change in a conventional commit, append an exclamation mark before the colon or include a BREAKING CHANGE footer, which signals the automated release tooling to increment the major version number.

How do conventional commit types map to semantic versioning bumps?▼

Conventional commit types directly map to semantic versioning bumps: feat triggers a minor version increment, fix triggers a patch increment, and any breaking change triggers a major version increment for automated releases.

Can I use conventional commits to generate changelogs in my CI pipelines?▼

Yes, you can use conventional commits in your CI pipelines to automatically generate changelogs and automate releases, because the structured Git commit messages provide the required machine-readable history for release tooling.

What is the correct structure for a conventional commit message?▼

The correct structure for a conventional commit message requires a type, an optional scope in parentheses, a colon, and a description, such as feat(auth): add OAuth2 login capability, ensuring consistent machine-readable Git history.