skills.rest
dwhoban
dwhobanCOMMUNITY
Explore all skills by this author →
GitHub

conventional-commit

Generate standardized commit messages following the Conventional Commits specification.

Updated Aug 27, 2026
Search Tags:#git#developer tools#version control#commit#conventional commits#code
One-click install
npx skills add https://github.com/dwhoban/chanfana-vite-kumo --skill conventional-commit-dwhoban
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/dwhoban/chanfana-vite-kumo/tree/main/.agents/skills/conventional-commit
Command: npx skills add https://github.com/dwhoban/chanfana-vite-kumo --skill conventional-commit-dwhoban

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of standardized commit messages, ensuring consistency and clarity in your version control history.

Core Features & Use Cases

  • Structured Commit Messages: Guides users to create commit messages following the Conventional Commits specification.
  • Type, Scope, Description: Enforces the use of essential commit message components.
  • Optional Body and Footer: Allows for detailed explanations and issue tracking.
  • Use Case: A developer needs to commit a bug fix. They use this Skill to generate a fix(auth): resolve login redirect loop commit message, ensuring it's properly categorized and described.

Quick Start

Use the conventional-commit skill to generate a commit message for a new feature that improves user authentication.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema
How do I generate conventional commit messages for git version control?▼

To generate conventional commit messages, structure your git commits with specific types, scopes, and descriptions. This ensures version control compliance, improves project maintainability, and enables automated changelog generation.

What are the required components of a conventional commit message?▼

Conventional commit messages require a type, scope, and description to categorize changes accurately. Optional body and footer sections can be added for detailed explanations and issue tracking references.

Can I use conventional commits to automate my project changelog generation?▼

Yes, conventional commits facilitate automated changelog generation by enforcing standardized commit message formats. Structured commit types and scopes allow tools to parse version control history and generate changelogs automatically.

How do I write a bug fix commit message using the conventional commits specification?▼

To write a bug fix commit message, use the fix type with an optional scope and a clear description. For example, generating a commit like fix(auth): resolve login redirect loop properly categorizes the change for version control.

Do I need any developer tools or dependencies installed to format conventional commits?▼

No specific developer tools or dependencies are required to format conventional commits. The specification relies on structuring commit types, scopes, and descriptions directly within your standard version control workflow.

Related Skills

Explore More Software Engineering Skills→
lexicalninjalexicalninja
2

git-commit-helper

Analyze staged changes to generate conventional commit messages.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
keshavraj936keshavraj936

lint-and-validate

Lint and statically analyze Node.js and Python code modifications.

Community
Intermediate
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced