Enforces conventional commit standards and branch management best practices for cleaner project history.

Install

mkdir -p .claude/skills/git && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1102" && unzip -o skill.zip -d .claude/skills/git && rm skill.zip

Installs to .claude/skills/git

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Git commits and branches using Epicenter conventions. Use when staging files, writing commit messages, splitting commits, checking standalone commits, creating branches, or inspecting commit history. For pull request titles and bodies, use the pull-request skill.
263 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • →Stage files for version control
  • →Format commit messages using conventional commit standards
  • →Apply specific commit types such as feat, fix, docs, or refactor
  • →Define optional scopes for localized component changes
  • →Document breaking changes using the footer syntax
  • →Create and manage branch structures

How it works

The skill enforces a specific commit message structure consisting of a type, optional scope, and description. It requires the use of imperative mood and specific formatting rules to ensure history remains auditable and compatible with automated versioning.

Inputs & outputs

You give it
Uncommitted file changes and descriptive intent
You get back
A formatted commit message and staged git state

When to use git

  • →Writing a conventional commit message
  • →Splitting complex changes into small commits
  • →Checking commit types and scopes

About git

Facilitates Git operations by enforcing conventional commit formatting, managing branch structure, and ensuring individual commits are reviewable. It helps maintain a clean, standardized project history suitable for automated versioning.

Git commit and pull request guidelines using conventional commits. Use when creating commits, writing commit messages, creating PRs, or reviewing PR descriptions.

When not to use it

  • →Writing pull request titles or descriptions
  • →Managing changelog entries or issue references
  • →Defining merge strategies

Limitations

  • →Does not handle pull request metadata or merge strategy
  • →Requires manual intervention for major version bumps
  • →Prohibits inclusion of AI-generated watermarks or tool attribution

How it compares

Unlike manual commit writing, this skill mandates strict adherence to conventional commit types and specific footer requirements for breaking changes to maintain a standardized project history.

Compared to similar skills

git side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git (this skill)85moReviewBeginner
resolve-conflicts8112moReviewIntermediate
dependency-upgrade268moReviewIntermediate
git-commits217moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry