commit

Enforce conventional commit format for git commit messages.

1|Updated Jan 13, 2026

Search Tags:#git #messaging #workflow #commit #version-control #conventional-commits

Ready to run

npx skills add https://github.com/osocode/code-tools-bootstrap --skill commit-osocode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/osocode/code-tools-bootstrap/tree/main/skills/generated/claude-code/commit
Command: npx skills add https://github.com/osocode/code-tools-bootstrap --skill commit-osocode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill standardizes git commit messages by enforcing the conventional commit format, reducing ambiguity and enabling automated changelog generation.

Core Features & Use Cases

Enforce commit type, optional scope, and a concise subject.
Provide examples and validation to guide developers during commit creation and review.
Use Case: When preparing releases, teams rely on consistent commit messages to generate changelogs and track changes.

Quick Start

Activate the skill and draft a sample commit message to test the rules, e.g., feat(auth): add OAuth2 login.

Frequently Asked Questions about commit

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

FAQPage Schema

What are conventional commits and why use them for git version control?▼

Conventional commits standardize git commit history by enforcing a structured format for type, optional scope, and subject length. This messaging workflow reduces ambiguity and enables automated changelog generation for version control.

How do I format a git commit message to pass conventional commit review?▼

To format a git commit message, enforce a specific commit type, an optional scope, and a concise subject. You must also wrap the commit body at 72 characters and use proper footer references to pass conventional commit validation.

Can I enforce conventional commit rules across multiple modules for my team?▼

Yes, you can enforce conventional commit rules across multiple modules for your team. The standardization covers commit creation, messaging, and review workflows, ensuring consistent git history for individual developers and teams.

Does the conventional commit format require a specific subject length and body wrap?▼

Yes, the conventional commit format requires a concise subject and enforces a 72-character wrap for the commit body. It also validates proper commit type, optional scope usage, and footer references.

What is the best way to generate changelogs from git commit history?▼

The best way to generate changelogs is to standardize git commit history by enforcing the conventional commit format. Consistent commit messaging allows teams to reliably track changes and automate changelog generation during releases.