commit

Generate Conventional Commits messages with validated type, scope, subject length, and body wrapping.

1|1|Updated Jan 6, 2026

Search Tags:#git #commit #formatting #conventional-commits #subject-line #body-wrap

Ready to run

npx skills add https://github.com/sontek/agent-skills --skill commit-sontek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/sontek/agent-skills/tree/main/plugins/agent-skills/skills/commit
Command: npx skills add https://github.com/sontek/agent-skills --skill commit-sontek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes commit messages by enforcing conventional commits and best practices, improving git history readability and automation-friendly formatting.

Core Features & Use Cases

Enforce subject length, wrapping, and type/scope formatting according to the Conventional Commits spec.
Provide templates and examples for common commit types (feat, fix, docs, perf, refactor).
Align commits with PRs and release workflows to enable reliable changelogs and automation.

Quick Start

Use this skill to generate a well-formed commit message for a new feature or bug fix.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I format git commit messages using conventional commits?▼

To format git commit messages using conventional commits, you generate a structured message with a type, scope, and subject. This enforces subject length and body wrapping to maintain a clean, machine-readable git history.

What is the conventional commits specification for a git history?▼

The conventional commits specification for a git history is a formatting standard that defines commit types like feat and fix. It uses a structured type, scope, subject, and body to make commit logs machine-readable and automation-friendly.

How do I generate a conventional commit message for a bug fix?▼

You generate a conventional commit message for a bug fix by using the fix type template. The skill provides templates for common scenarios like feat and fix, validating subject length and body wrapping to ensure proper formatting.

Does enforcing conventional commits support PR and release workflows?▼

Yes, enforcing conventional commits supports PR and release workflows. By standardizing commit messages with a well-structured type and scope, it enables reliable changelog generation and aligns commits with automated release processes.

What are the limitations of standardizing git commits with conventional commits?▼

A limitation of standardizing git commits is that it requires strict adherence to type, scope, subject length, and body wrapping validation. Teams must consistently apply these conventional commit templates to avoid breaking automated changelog and release workflows.