git-commit-pro

Generate conventional commit messages with type, scope, and description.

Updated Mar 27, 2026

Search Tags:#git #workflow #commit #branching #conventional-commits #pr-description #code-history

Ready to run

npx skills add https://github.com/goodstoriesworld/coco-agent-skills --skill git-commit-pro-goodstoriesworld

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams struggle with inconsistent commit messages and unclear PR descriptions, which makes code history hard to read and review.

Core Features & Use Cases

Enforces the Conventional Commits specification for all messages
Guides scope, type, and description formatting to keep history readable
Assists with drafting clear PR descriptions and branch naming conventions

Quick Start

Produce a conventional commit message for a new feature in the format feat(scope): description

Frequently Asked Questions about git-commit-pro

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

FAQPage Schema

How do I write conventional commit messages for my git workflow?▼

Conventional commit messages follow a structured format with a type, optional scope, and short description, such as feat(scope): description. This specification enforces consistent formatting to keep your git history readable and easier to review.

What is the conventional commits specification and when do I need it?▼

The conventional commits specification is a standard for structuring commit messages with types like feat or fix. You need it when your team struggles with inconsistent commit messages and wants to maintain a clean, organized code history.

How do I create a clear PR description from my branch history?▼

You can draft clear PR descriptions by applying the conventional commits specification to your branch history. This approach guides scope, type, and description formatting to ensure your pull request context is highly readable for reviewers.

What is the best way to organize git branches for software development?▼

The best way to organize git branches is by applying consistent branch naming conventions alongside the conventional commits specification. This combination ensures your code history remains structured and readable across your software development workflow.

Can I enforce conventional commit formatting across my entire code history?▼

Yes, you can enforce conventional commit formatting across your code history by applying the specification's type, scope, and description rules to every commit. This maintains a standardized and clean git history for all team members.