git-commits-branches

Enforce conventional commit types and branch naming formats for team workflows.

2|1|Updated Jan 20, 2026

Search Tags:#commit #branching #lint #code-review #git-workflow #version-control #conventional-commits

Ready to run

npx skills add https://github.com/sraloff/gravityboots --skill git-commits-branches

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commits-branches
Source: https://github.com/sraloff/gravityboots/tree/main/.agent/skills/git-commits-branches
Command: npx skills add https://github.com/sraloff/gravityboots --skill git-commits-branches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce consistent commit messages and branch naming to improve traceability and collaboration.

Core Features & Use Cases

Conventional commits: Use type(scope): description. Types: feat, fix, docs, style, refactor, test, chore.
Scope: Lowercase, concise (for example auth, header).
Body: Optional short description of why (not just what) if the change is complex.
Branch naming: Format: type/short-description (for example feat/add-login, fix/nav-bug). Separators: Use hyphens.
Atomic commits: One logical change per commit. Do not squash unrelated fixes.
Verification: Ensure tests and lint pass before committing.

Quick Start

Apply the conventional commit rules and branch naming conventions to your next feature work.

Frequently Asked Questions about git-commits-branches

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

FAQPage Schema

How do I enforce conventional commits and branch naming across a development team?▼

You can enforce conventional commits and branch naming by applying a standardized type set, scope rules, and branch naming format like type/short-description. This ensures consistent messages and traceability across feature development and bug fixes.

What is the correct format for conventional commit messages and branch names?▼

The correct format for commits is type(scope): description, using types like feat, fix, or docs. Branch names should follow type/short-description with hyphens, such as feat/add-login or fix/nav-bug, keeping scopes lowercase and concise.

How do I write atomic commits during feature development and code review?▼

To write atomic commits, include one logical change per commit and avoid squashing unrelated fixes. You should also verify that tests and lint pass before committing, adding an optional body to explain why complex changes were made.

Can I use custom commit types beyond the standard set for version control workflows?▼

The workflow imposes a specific commit type set: feat, fix, docs, style, refactor, test, and chore. It focuses on standardizing messages and branch names to improve collaboration rather than supporting fully custom commit types.

Why do my git branch names need hyphens as separators in a branch-based workflow?▼

Git branch names need hyphens as separators to maintain a standardized type/short-description format. Using hyphens ensures predictable, machine-readable branch naming that aligns with conventional commit types during PR reviews.

What's the best way to standardize git workflow for pull requests and pre-merge verification?▼

The best way to standardize git workflow is to impose commit type rules, scope naming conventions, and branch formats. Ensure tests and lint pass before committing, and maintain atomic commits to streamline pre-merge verification.