How do I install the Git Commit skill?

Run npx skillmds@latest add ricoberger/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. 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?

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

Git Commit by ricoberger — Agent Skill

Name: Git Commit
Author: ricoberger

File contents

Git Commit Messages

Write commit messages following the Conventional Commits specification.

Format

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Code style (formatting, no logic change)
`refactor`	Code change that neither fixes a bug nor adds a feature
`perf`	Performance improvement
`test`	Adding or correcting tests
`build`	Build system or external dependencies
`ci`	CI configuration
`chore`	Maintenance tasks
`revert`	Reverts a previous commit

Rules

Use imperative mood in description ("add feature" not "added feature")
Do not end description with a period
Keep description under 72 characters
Separate subject from body with a blank line
Use the body to explain intent, nuances, gotchas, or background behind the change — not a paraphrase of the diff
Wrap the body at 72 characters, except for long URLs, code, or fenced blocks which may exceed the limit

Breaking Changes

Add ! after type/scope or include BREAKING CHANGE: in footer:

feat(api)!: remove deprecated endpoints

BREAKING CHANGE: The /v1/users endpoint has been removed.

Scope

Optional. Use to specify area of change (e.g., api, ui, auth, db).

---name: git-commitdescription: This skill should be used BEFORE running any git commit command. Triggers when about to run `git commit`. Ensures commit messages follow Conventional Commits specification.---# Git Commit MessagesWrite commit messages following the Conventional Commits specification.## Format```<type>(<scope>): <description>[optional body][optional footer(s)]```## Types| Type | Purpose || ---------- | ------------------------------------------------------- || `feat` | New feature || `fix` | Bug fix || `docs` | Documentation only || `style` | Code style (formatting, no logic change) || `refactor` | Code change that neither fixes a bug nor adds a feature || `perf` | Performance improvement || `test` | Adding or correcting tests || `build` | Build system or external dependencies || `ci` | CI configuration || `chore` | Maintenance tasks || `revert` | Reverts a previous commit |## Rules1. Use imperative mood in description ("add feature" not "added feature")2. Do not end description with a period3. Keep description under 72 characters4. Separate subject from body with a blank line5. Use the body to explain intent, nuances, gotchas, or background behind the change — not a paraphrase of the diff6. Wrap the body at 72 characters, except for long URLs, code, or fenced blocks which may exceed the limit## Breaking ChangesAdd **!** after type/scope or include **BREAKING CHANGE:** in footer:```feat(api)!: remove deprecated endpointsBREAKING CHANGE: The /v1/users endpoint has been removed.```## ScopeOptional. Use to specify area of change (e.g., `api`, `ui`, `auth`, `db`).

Frequently asked questions

Git Commit