git-conventional-commits

Enforce Conventional Commits formatting and branch naming in Git repositories.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/hreis00/cortex-library --skill git-conventional-commits-hreis00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-conventional-commits
Source: https://github.com/hreis00/cortex-library/tree/main/.github/skills/git-conventional-commits
Command: npx skills add https://github.com/hreis00/cortex-library --skill git-conventional-commits-hreis00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides guidelines for maintaining clear, structured, and meaningful Git history with proper commit message formatting and branch naming conventions. It helps prevent common pitfalls and ensures a coherent workflow that scales as the project grows.

Core Features & Use Cases

  • Commit Message Formatting: Offers structured commit message guidelines with examples and best practices.
  • Branch Naming: Specifies a pattern for naming branches to convey purpose and maintain consistency.
  • Branch Workflow: Provides guidance on the feature branch workflow, including creating, merging, and rebasing branches.
  • Squashing and Reverting: Instructions for squashing commits before merging and reverting bad commits safely.
  • Tools and Commands: Lists useful tools like commitlint and semantic-release that facilitate convention adherence.
  • Use Case: A project manager or developer can use this Skill to ensure that all team members follow the Git conventions, leading to a more maintainable codebase.

Quick Start

Run the git-conventional-commits skill to get guidelines on best practices for Git commit messages and branch naming.

Frequently Asked Questions about git-conventional-commits

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

FAQPage Schema
How do I format conventional commit messages in Git?

To format conventional commit messages, follow structured guidelines with a specific type, scope, and subject. This Skill provides examples and best practices to ensure proper commit message formatting.

What is the best way to name Git branches for feature workflows?

The best way to name Git branches is using a consistent pattern that conveys purpose. This Skill specifies branch naming conventions and provides guidance on feature branch workflows, including merging and rebasing.

Can I use conventional commits for projects of any size?

Yes, conventional commits are suitable for projects of any size. This Skill implements and enforces Conventional Commits to ensure a coherent workflow that scales as your project grows and maintains a readable codebase.

What tools work with conventional commits to enforce formatting?

Tools like commitlint and semantic-release facilitate convention adherence. This Skill lists useful tools and commands that help enforce Conventional Commits and automate associated workflows in your repository.

How do I squash commits and revert bad commits safely in Git?

To squash commits and revert bad commits safely, follow specific instructions for squashing before merging and reverting. This Skill provides guidance on these operations to maintain a clean and structured Git history.