Skip to content
Back to skills

Git Commit Helper

ASecurity

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.

  • 33 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
documentationgogitapidatabasedocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add dvcrn/openclaw-skills-marketplace --skill git-commit-helper --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Commit Helper?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Commit Helper
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dvcrn-git-commit-helper/badge)](https://www.skillsdirectory.com/skills/dvcrn-git-commit-helper)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: git-commit-helper
description: "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

## 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](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
```

Files in this skill

  • SKILL.md2.1 KB
  • references/modules.md488 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…