How do I install the Git Commit Helper skill?

Run npx skillmds@latest add dvcrn/git-commit-helper 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 Helper safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit Helper?

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 Helper free to use?

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

Who published Git Commit Helper?

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

Git Commit Helper by dvcrn — Agent Skill

Name: Git Commit Helper
Rating: 4.5 (4 reviews)
Author: dvcrn

Git Commit Helper

Generate standardized git commit messages following Conventional Commits format. Use this skill when the user asks to commit code, write a commit message, or create a git commit. Enforces team conventions for type prefixes, scope naming, message length, and breaking change documentation.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

Git Commit Message Guide

Format

Every commit message MUST follow this structure:

<type>(<scope>): <subject>

[optional body]

[optional footer]

Type (required)

Type	When to use
feat	New feature or capability
fix	Bug fix
docs	Documentation only
refactor	Code change that neither fixes nor adds
test	Adding or updating tests
chore	Build, CI, tooling changes

Scope (required)

Scope MUST be a real module name from this project. See references/modules.md for the full list.

If unsure of the scope, check the file paths being changed — the top-level directory is usually the correct scope.

Subject (required)

Imperative mood: "add feature" not "added feature"
No period at the end
Max 72 characters total (including type and scope prefix)
Lowercase first letter

Body (optional)

Explain WHY, not WHAT (the diff shows what changed)
Wrap at 72 characters
Separate from subject with blank line

Breaking Changes

If the commit introduces a breaking change, add footer:

BREAKING CHANGE: <description of what breaks and migration path>

Examples

Good:

feat(auth): add JWT token refresh endpoint

Tokens now auto-refresh 5 minutes before expiry.
Previously users had to re-login after token expiration.

fix(parser): handle empty input without crashing

refactor(db): extract connection pooling to separate module

BREAKING CHANGE: DatabaseClient constructor no longer accepts
pool config. Use PoolConfig.create() instead.

Bad:

updated some stuff          ← no type, no scope, vague
feat: Add new Feature.      ← capitalized, period, missing scope
fix(misc): various fixes    ← "misc" is not a real module

---name: git-commit-helperdescription: Generate standardized git commit messages following Conventional Commits format. Use this skill when the user asks to commit code, write a commit message, or create a git commit. Enforces team conventions for type prefixes, scope naming, message length, and breaking change documentation.---# Git Commit Message Guide## FormatEvery commit message MUST follow this structure:```<type>(<scope>): <subject>[optional body][optional footer]```## Type (required)| Type | When to use ||------|-------------|| feat | New feature or capability || fix | Bug fix || docs | Documentation only || refactor | Code change that neither fixes nor adds || test | Adding or updating tests || chore | Build, CI, tooling changes |## Scope (required)Scope MUST be a real module name from this project.See [references/modules.md](references/modules.md) for the full list.If unsure of the scope, check the file paths being changed — the top-level directory is usually the correct scope.## Subject (required)- Imperative mood: "add feature" not "added feature"- No period at the end- Max 72 characters total (including type and scope prefix)- Lowercase first letter## Body (optional)- Explain WHY, not WHAT (the diff shows what changed)- Wrap at 72 characters- Separate from subject with blank line## Breaking ChangesIf the commit introduces a breaking change, add footer:```BREAKING CHANGE: <description of what breaks and migration path>```## Examples**Good:**```feat(auth): add JWT token refresh endpointTokens now auto-refresh 5 minutes before expiry.Previously users had to re-login after token expiration.``````fix(parser): handle empty input without crashing``````refactor(db): extract connection pooling to separate moduleBREAKING CHANGE: DatabaseClient constructor no longer acceptspool config. Use PoolConfig.create() instead.```**Bad:**```updated some stuff ← no type, no scope, vaguefeat: Add new Feature. ← capitalized, period, missing scopefix(misc): various fixes ← "misc" is not a real module```

Frequently asked questions