skills.rest
Unique-AG
Unique-AGOFFICIAL
Explore all skills by this author →
GitHub

git-conventional-commits

Enforce conventional commit message format with type, scope, and description.

5|3|Updated Jun 18, 2024
Search Tags:#git#branch-management#version-control#conventional-commits#commit-messages#coding-best-practices#clean-commit-history
One-click install
npx skills add https://github.com/Unique-AG/ai --skill git-conventional-commits-unique-ag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventional-commits
Source: https://github.com/Unique-AG/ai/tree/main/.claude/skills/git-conventional-commits
Command: npx skills add https://github.com/Unique-AG/ai --skill git-conventional-commits-unique-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates guidance and enforcement of conventional commit messages in a Git repository.

Core Features & Use Cases

  • Enforces commit type categories: chore, ci, deploy, docs, feat, fix, improvement, refactor, test
  • Guides scope and description formatting with <type>(scope): description
  • Improves repository history readability and changelog generation

Quick Start

Draft your next commit as 'feat(api): add login endpoint' following the conventional commits format.

Frequently Asked Questions about git-conventional-commits

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?▼

Conventional commits format Git messages using structured types like feat, fix, docs, and chore to standardize repository history. It applies the <type>(scope): description pattern to automate changelog generation and improve commit readability.

What is the conventional commits format for writing clean Git commit messages?▼

Conventional commits format Git messages using structured types like feat, fix, docs, and chore to standardize repository history. It applies the <type>(scope): description pattern to automate changelog generation and improve commit readability.

How do I write a conventional commit message with a scope for a new feature?▼

Use the conventional commits format <type>(scope): description, such as feat(api): add login endpoint. This structure standardizes commit history, aligns branch naming, and clarifies PR descriptions for software development workflows.

Does conventional commits validation support chore and ci commit types?▼

Yes, conventional commits validation supports chore, ci, deploy, docs, feat, fix, improvement, refactor, and test types. It guides scope and description formatting to ensure consistent version-control practices and clean repository history.

What's the best way to standardize Git commit history for team collaboration?▼

Standardize Git commit history by enforcing conventional commit messages with consistent types and scopes. This practice improves repository history readability, aligns branch management, and enables automated changelog generation for teams.

Related Skills

Explore More Software Engineering Skills→
buiminhduc23011buiminhduc23011

awf-commit

Standardize git commit messages using type(scope): description format.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
GolferGeekGolferGeek

Orchestrator Git Standards

Enforce conventional branch names, commit messages, and repository organization for Git workflows.

Community
Basic
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate