skills.rest
dashed
dashedCOMMUNITY
Explore all skills by this author →
Website𝕏@dasheddashedGitHub

conventional-commits

Create Git commit messages following the specified format and conventions.

22|6|Updated Nov 22, 2025
Search Tags:#git#workflow#changelog#commit#semantic-versioning#release-notes#conventional-commits
One-click install
npx skills add https://github.com/dashed/claude-marketplace --skill conventional-commits-dashed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/dashed/claude-marketplace/tree/main/plugins/conventional-commits
Command: npx skills add https://github.com/dashed/claude-marketplace --skill conventional-commits-dashed

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Conventional commits provide a standard for commit messages to convey intent and impact, improving changelog generation and versioning.

Core Features & Use Cases

  • Enforces a consistent commit message format across a project.
  • Supports types like feat, fix, docs, style, refactor, perf, test, build, ci, chore.
  • Useful for automatic release notes and semantic versioning workflows.

Quick Start

To format a commit description, apply a type prefix (e.g., feat, fix) followed by an optional scope and a concise description. Example: git commit -m 'feat(auth): add login capability'

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 automatic changelog generation?▼

To format git commit messages for changelog generation, apply a type prefix like feat or fix, followed by an optional scope and a concise description. This enforces a consistent commit message format across your project.

What is a conventional commit and when do I need it for semantic versioning?▼

A conventional commit is a standardized message format that conveys intent and impact. You need it for semantic versioning workflows to automatically determine release notes and version bumps from types like feat or fix.

How do I write a git commit message for a breaking change?▼

To write a git commit message for a breaking change, use a type prefix such as feat or fix and include a description that signals the breakage. This ensures the change is captured correctly for automatic release notes.

Do I need external tooling to use conventional commits in my git workflow?▼

No external tooling is required to use conventional commits in your git workflow. It operates within standard git workflows to format commit messages using types like feat, fix, docs, style, refactor, perf, test, build, ci, and chore.

What commit types are supported for structured software development workflows?▼

Supported commit types for structured software development workflows include feat, fix, docs, style, refactor, perf, test, build, ci, and chore. These types help convey intent for automatic release notes and semantic versioning.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
zhangzhang-111-izhangzhang-111-i
2

changelog-generator

Generate changelog entries from Conventional Commits in markdown or JSON.

Community
Intermediate
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate