skills.rest
morgs32
morgs32COMMUNITY
Explore all skills by this author →
WebsiteGitHub

conventional-commits

Enforce Conventional Commits format with type, scope, and description.

Updated Jun 30, 2026
Search Tags:#git#linting#commit messages#semantic-versioning#release-notes#conventional-commits
One-click install
npx skills add https://github.com/morgs32/skills --skill conventional-commits-morgs32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/morgs32/skills/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/morgs32/skills --skill conventional-commits-morgs32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes commit messages by enforcing the Conventional Commits specification, reducing ambiguity and enabling automated release notes.

Core Features & Use Cases

  • Enforces conventional commit types (fix, feat, docs, style, refactor, perf, test, build, ci, chore, revert) to ensure each commit has a valid type.
  • Supports optional scope and concise descriptions to improve clarity.
  • Facilitates automated changelog generation and semantic versioning across projects.
  • Use Case: Teams stewarding multiple packages or services can maintain uniform messaging, simplifying reviews and releases.

Quick Start

Use the Conventional Commits format for all commits. Example: feat(auth): add OAuth login flow.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema
How do I standardize git commit messages for automated release notes?▼

You can standardize git commit messages by enforcing the Conventional Commits format, which uses a defined type, optional scope, and imperative description to enable automated changelog generation and semantic versioning.

What is the Conventional Commits format for structuring commit messages?▼

The Conventional Commits format structures commit messages with a specific type like feat or fix, an optional scope, and a concise imperative description, reducing ambiguity across repository workflows.

How do I generate automated changelogs using semantic versioning?▼

Automated changelogs are generated by applying the Conventional Commits specification to your commit messages, allowing tooling to parse commit types and facilitate semantic versioning across projects.

Can I use conventional commits for multiple packages or services?▼

Yes, teams stewarding multiple packages or services can use conventional commits to maintain uniform messaging, which simplifies code reviews and release management across different projects.

What commit types are supported by the Conventional Commits specification?▼

The Conventional Commits specification supports types including fix, feat, docs, style, refactor, perf, test, build, ci, chore, and revert to ensure every commit has a valid category.

Does enforcing commit message conventions require validation tooling?▼

Enforcing commit message conventions supports validation tooling to ensure compliance with the Conventional Commits format, enabling consistent messaging for features, fixes, and documentation changes.

Related Skills

Explore More Software Engineering Skills→
PackmindHubPackmindHub
306

git-commit-guidelines

Generate Git commit messages combining GitMoji prefixes with Conventional Commits and Co-Authored-By for AI-assisted commits.

Official
Basic
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced
jpoutrinjpoutrin
14

git-commits

Enforce Conventional Commits format for Git commit messages.

Community
Basic