git

name	git
description	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.
metadata	{"author":"epicenter","version":"2.0"}

Git Commit Guidelines

Related Skills: See standalone-commits for making each commit reviewable and auditable and for ordering multi-file changes into dependency-ordered waves. See pull-request for PR titles, descriptions, changelog entries, issue references, and merge guidance.

PR Boundary

PR titles, PR bodies, changelog entries, issue links, username verification, CODEOWNERS notes, and merge strategy belong to pull-request.

References

This skill keeps its rules inline. For PR work, use pull-request.

Conventional Commits Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

• feat: New features (correlates with MINOR in semantic versioning)
• fix: Bug fixes (correlates with PATCH in semantic versioning)
• docs: Documentation only changes
• refactor: Code changes that neither fix bugs nor add features
• perf: Performance improvements
• test: Adding or modifying tests