commit

Generate conventional commit messages using the type(scope): summary format.

6|1|Updated Nov 23, 2023

Search Tags:#git #workflow #commit #code-quality #version-control #conventional-commits #message-format

Ready to run

npx skills add https://github.com/gmcabrita/dotfiles --skill commit-gmcabrita

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gmcabrita/dotfiles/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill commit-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create consistent, conventional commit messages so changes are clearly described and easy to review, track, and release.

Core Features & Use Cases

Enforces the Conventional Commits format for all commits, guiding type, optional scope, and a concise summary.
Supports optional body paragraphs for additional context and rationale when needed.
Use Case: when working on a feature or bug fix across multiple files, generate a standardized commit that includes the scope and type to improve traceability.

Quick Start

Create a conventional commit message for your changes using the format type(scope): summary.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I write conventional commit messages for git version control?▼

Conventional commit messages follow the format type(scope): summary, requiring a type, an optional scope, a concise subject under 72 characters, and an optional body for additional context to ensure changes are easy to track and release.

What is the conventional commits format for features, fixes, and refactors?▼

The conventional commits format uses a required type like feat, fix, or refactor, paired with an optional scope and a concise summary, to categorize code changes and maintain consistent, traceable commit histories across software development workflows.

How do I enforce a consistent commit message format across my software development workflow?▼

You can enforce a consistent commit message format by applying rules that require a specific type, an optional scope, and a subject under 72 characters, preventing non-standard commits from being pushed to version control.

Can I include additional context and rationale in a conventional commit message?▼

Yes, conventional commit messages support an optional body paragraph where you can include additional context, rationale, and detailed explanations for changes spanning multiple files or complex features.

Does this conventional commit format require any specific git dependencies or components?▼

No specific dependencies or components are required. The conventional commit format is applied directly during your software development workflow to generate standardized messages without needing external tools or plugins.