conventional-commits

Reference the Conventional Commits 1.0.0 specification for commit message structure.

Updated Aug 27, 2026

Search Tags:#code quality #git #developer tools #versioning #conventional commits #commits

Ready to run

npx skills add https://github.com/tmsjngx0/mindcontext-core --skill conventional-commits-tmsjngx0

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/tmsjngx0/mindcontext-core/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/tmsjngx0/mindcontext-core --skill conventional-commits-tmsjngx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear reference for writing consistent and informative commit messages, improving code history readability and enabling automated changelog generation.

Core Features & Use Cases

Commit Message Format: Details the standard structure including type, scope, description, body, and footers.
Commit Types: Explains the purpose of each commit type (feat, fix, docs, etc.).
Breaking Changes: Illustrates how to denote breaking changes.
Use Case: When you're about to commit a new feature, you can quickly consult this Skill to ensure your commit message follows the feat: add user authentication format, making your Git history clean and understandable.

Quick Start

Consult the conventional commits skill for guidance on writing commit messages.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema

What is the standard structure for conventional commits in git?▼

Conventional commits structure includes a type, optional scope, description, body, and footers. This format standardizes git commit messages to improve code history readability and enable automated changelog generation.

How do I denote breaking changes in a conventional commit message?▼

Denote breaking changes in a conventional commit message by adding a "BREAKING CHANGE" footer or appending an exclamation mark after the type, such as "feat!". This signals a major semantic version increment.

What commit types should I use for features and bug fixes?▼

Use "feat" for introducing a new feature and "fix" for patching a bug. Other conventional commit types include "docs" for documentation, ensuring a clean and understandable Git history.

How do conventional commits relate to semantic versioning?▼

Conventional commits directly drive semantic versioning: "feat" triggers a minor version bump, "fix" triggers a patch, and breaking changes mandate a major version release, automating version management.

When do I need to use a scope in my commit message format?▼

Use a scope in your commit message format to specify the affected module or component, such as "feat(auth): add login". It adds context to the commit type for better code history organization.

Can I use conventional commits to generate automated changelogs?▼

Yes, conventional commits provide a structured format that enables automated changelog generation. By parsing the commit types and breaking changes, tools can automatically derive release notes and version bumps.