git-workflow

Enforce Conventional Commits style with type, scope, and 72-character subject limits.

13|Updated Mar 15, 2019

Search Tags:#git #workflow #versioning #commit #review #code-quality #conventional-commits

Ready to run

npx skills add https://github.com/WTFox/dotfiles --skill git-workflow-wtfox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/WTFox/dotfiles/tree/main/claude/.claude/skills/git-workflow
Command: npx skills add https://github.com/WTFox/dotfiles --skill git-workflow-wtfox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps Git history readable and meaningful by enforcing a consistent commit message standard.

Core Features & Use Cases

Enforces the Conventional Commits standard across teams, guiding type, scope, and subject formatting.
Provides templates and examples for common types (feat, fix, docs, chore, etc.) and guidance for PR descriptions and changelogs.
Helps teams quickly generate well-formed messages to improve changelog clarity and code reviews.

Quick Start

Generate a conventional commit message for the next change.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I enforce conventional commits for my Git workflow?▼

To enforce conventional commits in your Git workflow, this Skill applies type, scope, and subject formatting rules to every message. It provides templates for common types like feat and fix to keep your Git history consistently structured.

What is the conventional commits standard for Git commit messages?▼

The conventional commits standard structures Git commit messages by enforcing specific type, scope, and subject formatting rules. It uses common types like feat, fix, docs, and chore to keep history readable and meaningful across software projects.

How do I generate a conventional commit message for my code review?▼

You generate a conventional commit message for code review by applying enforced type, scope, and subject formatting rules. This Skill guides message creation to improve changelog clarity and ensure well-formed PR descriptions.

Does the conventional commits standard have a character limit for Git messages?▼

Yes, the conventional commits standard enforced here includes a 72-character limit per line. This applies to the subject formatting of your Git commit messages to ensure consistent readability across software projects.

Can I use conventional commits for changelog generation and PR descriptions?▼

Yes, you can use conventional commits for changelog generation and PR descriptions. The standard type and scope formatting provides templates and guidance that directly improve changelog clarity and support well-formed PR descriptions.