How do I install the Git Commit skill?

Run npx skillmds@latest add ivy00johns/git-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit?

ivy00johns (@ivy00johns) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit by ivy00johns — Agent Skill

Name: Git Commit
Rating: 4.666666666666667 (3 reviews)
Author: ivy00johns

Git Commit

Guide for creating git commits in this repository: conventional commit format, allowed types, and branch naming conventions. Use when staging changes and writing a commit message, creating a branch, or naming a branch. Trigger on: "commit", "create a commit", "git commit", "stage changes", "write a commit message", "make a commit", "branch name", "new branch", "create branch". Also use proactively whenever you are about to run `git commit` — even if the user did not explicitly mention this skill.

ivy00johns Updated Sep 22, 2026

File contents

Git Commit Conventions

Commit Message Format

type: short description in imperative mood

Optional body paragraph.

No scope — use feat: add X, not feat(module): add X.
Lowercase type and description.
Imperative mood: "add X", "fix Y", "remove Z" — not "added", "adding", "fixes".
No period at the end.
Max ~72 characters on the subject line.
Optional body (blank line after subject): use for context, not mechanics.

Allowed Types

Type	When to use
`feat`	New feature or behaviour
`fix`	Bug fix
`test`	Adding or fixing tests only
`docs`	Documentation only
`refactor`	Code change with no feature/fix
`chore`	Build, tooling, config, deps
`build`	Build system changes
`perf`	Performance improvement
`style`	Formatting, whitespace — no logic change
`revert`	Reverts a previous commit

Examples

A complete commit with body:

feat: add retry policy to HTTP client

Wrap outbound calls in a retry with exponential backoff so
transient failures from downstream services don't fail the request.

A minimal commit:

fix: handle null input in prompt builder

Subject-only quick reference:

test: add unit tests for retry backoff logic
chore: update dependencies
docs: document skill frontmatter spec
refactor: extract connection string builder to helper

Branch Naming

{type}/{short-description}

Use the commit type directly (feat, fix, chore, etc.) — not expanded forms.
Description uses hyphens to separate words, kept to 3–5 meaningful words.

Branch Name Examples

feat/add-query-meter-api
fix/api-client-retry-policy
chore/update-skill-frontmatter
docs/add-orchestrator-guide

Merge Strategy

PRs merge with a squash merge by default unless the branch has a meaningful commit history worth preserving.

Co-Authored-By Trailer

Commits in this repo end with a Co-Authored-By: Claude ... <noreply@anthropic.com> trailer and a Claude-Session: line. These are applied automatically from the agent's environment/system instructions — do not hand-type them into the message body, and do not invent or alter the email or session URL. Write your type: description subject and optional body as normal; the trailers are appended below the body, separated by a blank line, as the last lines of the message.

Quick Checklist

Subject line: type: description (lowercase, imperative, no scope, no period)
Type is one of the allowed types above
Optional body explains the why, not the what
Branch: type/short-description

Anti-Pattern

Forbidden: Amending commits unless the user explicitly asks. After a pre-commit hook failure, create a NEW commit.

---name: git-commitdescription: Guide for creating git commits in this repository: conventional commit format, allowed types, and branch naming conventions. Use when staging changes and writing a commit message, creating a branch, or naming a branch. Trigger on: "commit", "create a commit", "git commit", "stage changes", "write a commit message", "make a commit", "branch name", "new branch", "create branch". Also use proactively whenever you are about to run `git commit` — even if the user did not explicitly mention this skill.---# Git Commit Conventions## Commit Message Format```texttype: short description in imperative moodOptional body paragraph.```- **No scope** — use `feat: add X`, not `feat(module): add X`.- **Lowercase** type and description.- **Imperative mood**: "add X", "fix Y", "remove Z" — not "added", "adding", "fixes".- **No period** at the end.- **Max ~72 characters** on the subject line.- Optional body (blank line after subject): use for context, not mechanics.### Allowed Types| Type | When to use ||---|---|| `feat` | New feature or behaviour || `fix` | Bug fix || `test` | Adding or fixing tests only || `docs` | Documentation only || `refactor` | Code change with no feature/fix || `chore` | Build, tooling, config, deps || `build` | Build system changes || `perf` | Performance improvement || `style` | Formatting, whitespace — no logic change || `revert` | Reverts a previous commit |### ExamplesA complete commit with body:```textfeat: add retry policy to HTTP clientWrap outbound calls in a retry with exponential backoff sotransient failures from downstream services don't fail the request.```A minimal commit:```textfix: handle null input in prompt builder```Subject-only quick reference:```texttest: add unit tests for retry backoff logicchore: update dependenciesdocs: document skill frontmatter specrefactor: extract connection string builder to helper```---## Branch Naming```text{type}/{short-description}```- Use the commit type directly (`feat`, `fix`, `chore`, etc.) — not expanded forms.- Description uses hyphens to separate words, kept to 3–5 meaningful words.### Branch Name Examples```textfeat/add-query-meter-apifix/api-client-retry-policychore/update-skill-frontmatterdocs/add-orchestrator-guide```---## Merge StrategyPRs merge with a **squash merge** by default unless the branch has a meaningful commit history worth preserving.---## Co-Authored-By TrailerCommits in this repo end with a `Co-Authored-By: Claude ... <noreply@anthropic.com>` trailer and a `Claude-Session:` line. These are applied automatically from the agent's environment/system instructions — do **not** hand-type them into the message body, and do not invent or alter the email or session URL. Write your `type: description` subject and optional body as normal; the trailers are appended below the body, separated by a blank line, as the last lines of the message.---## Quick Checklist- [ ] Subject line: `type: description` (lowercase, imperative, no scope, no period)- [ ] Type is one of the allowed types above- [ ] Optional body explains the *why*, not the *what*- [ ] Branch: `type/short-description`---## Anti-Pattern> **Forbidden:** Amending commits unless the user explicitly asks. After a pre-commit hook failure, create a NEW commit.

Frequently asked questions