skills.rest
NeuronioAzul
NeuronioAzulCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Conventional Commits

Enforce Conventional Commits rules for commit messages with types, scopes, and footers.

2|Updated Oct 4, 2025
Search Tags:#git#code review#versioning#developer workflow#conventional commits#commits
One-click install
npx skills add https://github.com/NeuronioAzul/vscode-ext_img-details --skill conventional-commits-neuronioazul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Conventional Commits
Source: https://github.com/NeuronioAzul/vscode-ext_img-details/tree/main/.agents/skills/conventional-commits
Command: npx skills add https://github.com/NeuronioAzul/vscode-ext_img-details --skill conventional-commits-neuronioazul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a standardized format for commit messages, making project history more readable, understandable, and automatable.

Core Features & Use Cases

  • Enforces Conventional Commits: Guides developers to write commit messages that follow a widely adopted standard.
  • Improves Readability: Ensures commit messages clearly indicate the type and scope of changes.
  • Enables Automation: Facilitates automated changelog generation and semantic versioning.
  • Use Case: When making a new feature, you can use this skill to ensure your commit message follows the feat(<scope>): <description> format, making it easy for others to understand the change at a glance.

Quick Start

Use the conventional commits skill to help write a commit message for a bug fix in the editor scope.

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

Standardize git commit messages by enforcing the Conventional Commits specification, which defines rules for commit types, scopes, descriptions, bodies, and footers to clarify project history and enable semantic versioning.

What is the conventional commits format for writing a bug fix message?▼

The conventional commits format for a bug fix uses the structure `fix(<scope>): <description>`, ensuring the commit type clearly indicates the change and facilitates automated changelog generation for developers.

How does a standardized commit history help with automated changelog generation?▼

A standardized commit history enables automated changelog generation by providing structured commit types and scopes that tools can parse reliably, turning structured git messages into readable release notes automatically.

How do I indicate a breaking change in a commit message?▼

Indicate a breaking change in a commit message by including specific guidance in the commit body or footer, following the Conventional Commits specification to ensure semantic versioning correctly bumps the major version.

Do I need any specific dependencies to use conventional commits in my developer workflow?▼

No specific dependencies are required to adopt conventional commits in your developer workflow, as the Skill operates independently to guide the structure of commit messages for better code review and readability.

Related Skills

Explore More Software Engineering Skills→
naj2rnaj2r

commit

Creates git commits with auto-generated messages and optional push.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate