Skip to main content
skill CX Codex

git-commit · fvadicamo — Claude Code skill: Conventional Commits, done right

A skill that writes git commits in Conventional Commits format with a type, a required scope and a short subject. Useful when the agent commits on your behalf.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add fvadicamo/dev-agent-skills --skill git-commit -a claude-code
Open on GitHub

What git-commit does

The skill builds the commit message for you. It first reads the last five commits with git log --oneline -5, then produces a line like type(scope): subject. Scope is required and uses kebab-case, for example validation, auth, cookie-service or api. The subject is an imperative verb, no trailing period, 50 characters max.

On top of the standard Conventional Commits types, the skill allows one extra: security, for vulnerability fixes and hardening. Multi-line commits go through a HEREDOC — headline, blank line, body as a list. Related changes are meant to land in a single focused commit, and vague messages such as "update code" or "changes" are rejected.

Before any of that, the skill checks the conventions in CLAUDE.md. If your project format differs, the project format wins. So in a repo with its own type names and scope rules, expect those instead of the default scheme. Extended per-type examples live in references/commit_examples.md.

What it helps with

  • write a commit message in Conventional Commits format
  • add the required kebab-case scope
  • block vague messages like "fix bug"
  • keep the subject line within 50 characters
  • format a multi-line commit with a HEREDOC body

Example prompts for the agent

  • commit the changes in the validation module
  • make a Conventional Commits commit for the auth fixes
  • stage the files and commit with the security type

How to install git-commit

1Skills CLI (Vercel)

npx skills add fvadicamo/dev-agent-skills --skill git-commit -a claude-code

2Manually: put the files in place

~/.claude/skills/git-commit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/git-commit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about git-commit

How do I install git-commit in Claude?

Run npx skills add fvadicamo/dev-agent-skills --skill git-commit -a claude-code. The skill file then lands at ~/.claude/skills/git-commit/SKILL.md.

What does git-commit do?

It creates git commits in Conventional Commits format with a type, a required scope and a short subject. It also enforces the project conventions found in CLAUDE.md.

Which commit types does the skill support?

The standard Conventional Commits types plus an extra security type for vulnerability fixes and hardening.

Source text

SKILL.md · MIT
---
name: git-commit
description: Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
---

# Git commit

Creates git commits following Conventional Commits format.

## Recent project commits

!`git log --oneline -5 2>/dev/null`

## Quick start

```bash
# 1. Stage changes
git add <files>

# 2. Create commit
git commit -m "type(scope): subject"
```

## Project conventions

- Scope is **required** (kebab-case): `validation`, `auth`, `cookie-service`, `api`
- Additional type beyond standard CC: `security` (vulnerability fixes or hardening)
- HEREDOC for multi-line commits:

```bash
git commit -m "$(cat <<'EOF'
feat(validation): add URLValidator with domain whitelist

Implement URLValidator class supporting:
- Domain whitelist enforcement
- Dangerous scheme blocking

Addresses Requirement 31
Part of Task 5.1
EOF
)"
```

## Important rules

- **ALWAYS** check CLAUDE.md conventions first - use project format if it differs
- **ALWAYS** include scope in parentheses
- **ALWAYS** use present tense imperative verb for the subject
- **NEVER** end subject with a period
- **NEVER** exceed 50 chars in the subject line
- **NEVER** use generic messages ("update code", "fix bug", "changes")
- Group related changes into a single focused commit

## References

- `references/commit_examples.md` - Extended examples by type, good/bad comparisons

© fvadicamo · MIT · fvadicamo/dev-agent-skills

Similar skills

All skills for Git and GitHub →

git-commit by other authors comes first.

git-commit official github This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits. 47,165installs git-commit ilteoood Reads your diff, picks the commit type and scope, and writes a Conventional Commits message. Handy when every commit ends up as fix or update. CX Codex +1 533installs summarize_git_diff danielmiessler This prompt reads a git diff and returns a short conventional-commits message plus a bulleted list of what changed. ★ 44,429repo stars git-commit-helper davila7 Reads your staged changes and drafts a commit message in conventional commits format. Handy when you cannot be bothered to phrase one yourself. 7,093installs Conventional Commit Message Generator jeff-nasseri Turns a git diff or a plain description of your changes into a commit message that follows the Conventional Commits spec. Handy when you can't be bothered to recall the format. GP ChatGPT ★ 174,597repo stars conventional-git samber Enforces Conventional Commits v1.0.0 rules for branch names and commit messages. Useful for parseable git history and automated changelogs on GitHub and GitLab. CX Codex +1 4,600installs git-workflow Netresearch DTT GmbH Automates branch workflows, Conventional Commits, and pull request checks. Guides agents through safe rebase steps and CI gates using GitHub CLI. CX Codex +1 722installs re0-git LilMGenius Rewrites a finished commit message to match the local Git log style. Run it after committing when the log should explain the change without opening a diff. CX Codex +1 1,300installs

From the same set2

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor