commits

Enforce Conventional Commits format with a template and shell validator.

22|1|Updated Jan 10, 2026

Search Tags:#git #changelog #templates #validation #semantic-versioning #conventional-commits #commit-messages

Ready to run

npx skills add https://github.com/itechmeat/llm-code --skill commits-itechmeat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commits
Source: https://github.com/itechmeat/llm-code/tree/main/skills/commits
Command: npx skills add https://github.com/itechmeat/llm-code --skill commits-itechmeat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill standardizes commit messages to improve changelog accuracy and semantic versioning across projects.

Core Features & Use Cases

Enforces the Conventional Commits structure: <type>[scope]: <description> to enable automated parsing.
Supports changelog integration and version bump guidance for release automation.
Provides templates and a lightweight validator to help teams validate messages in CI or local workflows.

Quick Start

To start using this skill, copy the provided templates and validator into your repository and integrate them into your workflow.

Copy assets/commit-msg.template as your commit message template.
Run or integrate assets/validate-commit-msg.sh in CI to enforce message format.
Optionally use a lint tool like commitlint for additional checks.

Frequently Asked Questions about commits

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

FAQPage Schema

How do I enforce conventional commits format across multiple repositories?▼

You can enforce conventional commits by copying a provided commit message template and running a lightweight shell validator script in your CI pipeline to check type, scope, length, and breaking change indicators.

What is the conventional commits structure needed for changelog automation?▼

The conventional commits structure requires the format <type>[scope]: <description>. This standardized structure enables automated parsing to support changelog integration and semantic versioning across projects.

Can I use a shell validator script to check git commit messages in CI?▼

Yes, you can integrate the provided shell validator script into your CI workflow to automatically check commit messages against the conventional commits standard before allowing changes to merge.

Do I need commitlint to validate conventional commit messages?▼

Commitlint is optional for additional checks. The Skill provides a lightweight shell validator script that handles core validation for type, scope, length, and breaking changes without external dependencies.

Why use conventional commits templates for semantic versioning?▼

Conventional commits templates standardize your commit history to enable automated parsing, which directly improves changelog accuracy and provides version bump guidance for release automation.

What's the best way to standardize git commit messages for automated parsing?▼

The best way is to apply a conventional commits template defining the <type>[scope]: <description> format, then enforce it with a shell validator script in your development workflow to ensure all messages conform.