git-commit

Enforce Conventional Commits format for git commits and PR/MR titles.

4|Updated Feb 23, 2026

Search Tags:#git #commit #scope #conventional-commits #pr-title #message-format #type-prefix

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commits provide a standardized format for git commits and PR/MR titles, enabling clear history, easier code reviews, and automation tooling compatibility. Not for PR workflows (git-pr), CI/CD status (git-ci), or git branch management.

Core Features & Use Cases

Enforces type-prefixes and scope usage for commits and PR/MR titles.
Ensures a consistent message structure to simplify changelogs, release notes, and automation.
Use Case: Teams adopt conventional commits to automatically generate changelogs and improve review clarity.

Quick Start

Format your next commit using a conventional type-prefix and optional scope to align with project conventions.

Frequently Asked Questions about git-commit

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

FAQPage Schema

What are conventional commits and why do I need a type prefix for git commit messages?▼

Conventional commits standardize git commit messages by requiring a type prefix, lowercase imperative description, and optional scope. This format ensures machine-parseable history, simplifying changelogs, release notes, and automation tooling compatibility.

How do I format a git commit message to follow conventional commits?▼

To format conventional commits, start your git commit message with a type prefix, add an optional scope, and use a lowercase imperative description. Following these rules ensures a consistent message structure for code reviews and automated release notes.

Does enforcing conventional commits work for both git commits and PR titles?▼

Yes, enforcing conventional commits applies to both everyday git commits and PR/MR titles. It ensures a consistent message structure across feature work, bug fixes, and documentation updates for individual and team projects.

When should I use breaking change rules and scopes in conventional commits?▼

Use breaking change rules and scopes in conventional commits to clearly communicate major modifications and component boundaries. This practice ensures machine-parseable history and improves review clarity for automated changelogs.

When should I not use conventional commits for git branch management or CI/CD?▼

Do not use conventional commits for CI/CD status checks, git branch management, or PR workflows. This standard specifically solves the lack of standardized commit messages for feature work, bug fixes, and documentation updates.

What is the best way to automate changelog generation using git commit history?▼

The best way to automate changelog generation is by enforcing conventional commits across your git commit history. Standardizing type prefixes and scopes creates a machine-parseable history that automation tooling can easily process.