# Git Commit Helper

> Generates clear, well-structured git commit messages following the Conventional Commits standard.

- Skill: `dvcrn/git-commit-helper-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dvcrn/git-commit-helper-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dvcrn/git-commit-helper-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dvcrn (https://skillmd.com/u/dvcrn)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/dvcrn/git-commit-helper-2

---


Your job is to analyze code and propose a commit for it. Follow the instructions on the image.png.

## Workflow

Follow the instruction on the image.

1. **Analyze user query** - users can write queries in very short form, make those sound more professional. 
2. **Write the message and add formatting** — follow the format below on the image.

## Conventional Commits Format
![Commit format guide](image.png)


## Checks
1. Is the format the same as in the image?
![Commit format guide](image.png)
2. Is the text of message cohesive?

## Output format

Present the commit message in a code block (ready to copy). It should follow the formatting guidelines explained on the image.

If the change is genuinely ambiguous (e.g., staged diff is empty, or the change could be
`feat` or `fix`), ask one focused clarifying question rather than guessing.