conventional-commit

Generate standardized commit messages following the Conventional Commits specification.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill conventional-commit-gabeujin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/Gabeujin/workspace-init-mcp/tree/main/awesome/skills/conventional-commit
Command: npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill conventional-commit-gabeujin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating standardized commit messages, ensuring consistency and clarity in your project's version history.

Core Features & Use Cases

  • Structured Commit Messages: Generates commits adhering to the Conventional Commits specification.
  • Guided Workflow: Provides clear instructions and examples for crafting type, scope, description, body, and footer.
  • Use Case: When you've finished a new feature, use this Skill to automatically generate a feat(api): add user authentication commit message, including a detailed body explaining the implementation.

Quick Start

Use the conventional-commit skill to generate a commit message for a bug fix.

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?

To generate conventional commit messages, this Skill guides you through structuring the type, scope, description, body, and footer according to the specification. It automatically formats your git commits to ensure version control history clarity.

What is the conventional commits format and when should I use it?

The conventional commits format is a structured specification for writing commit messages using types like feat or fix. You should use it to maintain consistent version history and enable automated changelog generation.

How do I write a structured commit message for a bug fix?

To write a structured commit message for a bug fix, use the guided workflow to generate a fix type with an optional scope and description. This ensures your bug fixes follow version control best practices.

Can I include a detailed body and footer in my conventional commits?

Yes, you can include optional bodies and footers in your conventional commits. The Skill provides clear instructions and examples for crafting these sections to explain your implementation details.

Does enforcing structured commit messages help with automated changelog generation?

Enforcing structured commit messages directly aids automated changelog generation by providing a predictable format. Standardized types and scopes allow tools to parse history and automatically generate release notes.