Skills
.Work. You
Rest

git-commits-branches

Community

Standardize git commits and branch naming.

Software Engineering#commit#branching#lint#code-review#git-workflow#version-control#conventional-commits
Authorsraloff
Version1.0.0
Installs0

System Documentation

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.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: git-commits-branches
Download link: https://github.com/sraloff/gravityboots/archive/main.zip#git-commits-branches

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.