git-conventions

Enforce conventional commit messages with required types and scopes.

10|Updated Mar 20, 2026

Search Tags:#git #workflow #versioning #commit #lint #conventional-commits #scopes

Ready to run

npx skills add https://github.com/mikeleppane/tursotui --skill git-conventions-mikeleppane

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-conventions
Source: https://github.com/mikeleppane/tursotui/tree/main/.claude/skills/git-conventions
Command: npx skills add https://github.com/mikeleppane/tursotui --skill git-conventions-mikeleppane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes git commit messages by enforcing scopes and conventional prefixes, improving history clarity, changelog generation, and automation.

Core Features & Use Cases

Enforces Conventional Commits structure: type(scope): subject with detailed body and footer guidance.
Enforces required scopes and a defined set of types (feat, fix, docs, perf, refactor, build, ci, chore) to ensure consistent messaging across the repo.
Use Case: enabling automated changelog tooling, code reviews, and impact analysis by parsing standardized commit messages.

Quick Start

Start applying the conventional commit format in every commit by choosing a type and scope and composing a concise subject following the <type>(<scope>): <subject> pattern.

Frequently Asked Questions about git-conventions

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

FAQPage Schema

How do I enforce conventional commit messages in a git repository?▼

To enforce conventional commit messages in git, apply the <type>(<scope>): <subject> pattern using defined types like feat, fix, docs, and refactor, alongside a mandatory scope to validate commit quality and standardize repository history.

What is the conventional commits format for staging changes and generating changelogs?▼

The conventional commits format for generating changelogs specifies a type, mandatory scope, and subject structure like <type>(<scope>): <subject>, paired with detailed body and footer guidance to enable automated changelog tooling and impact analysis.

Which git commit prefixes should I use for consistent versioning history?▼

For consistent versioning history, use the defined conventional commit prefixes: feat, fix, docs, perf, refactor, build, ci, and chore, ensuring every commit clearly communicates its purpose for automated parsing.

How do I structure a git commit message with scopes and a body?▼

Structure a git commit message by starting with <type>(<scope>): <subject>, then appending a detailed body explaining the change and a footer for metadata, ensuring scopes are mandatory to maintain consistent messaging across the repo.

Does enforcing conventional commits work for any software project repository?▼

Yes, enforcing conventional commits works for any software project repository where teams perform staging changes and commits, applying standardized types and mandatory scopes regardless of the specific platform to improve history clarity.