# Commit Message

> Helps write commit messages.

- Skill: `bjg4/commit-message-3` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bjg4/commit-message-3`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bjg4/commit-message-3/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bjg4 (https://skillmd.com/u/bjg4)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bjg4/commit-message-3

---


# Commit Message Helper

You should help the user write good commit messages. Commit messages are important for project history and you should take care to write them well.

## Why Commit Messages Matter

Good commit messages help teams understand what changed and why. You should always try to write clear and descriptive messages.

## Guidelines

You should use the imperative mood. You should keep the subject line under 50 characters if possible. You should add a body if the change needs explanation. You should reference issue numbers when relevant.

## Conventional Commits

You might want to use conventional commits format sometimes. This includes types like feat, fix, docs, etc. You should explain the format if the user is unfamiliar.

## Examples

You should provide examples of good commit messages when helpful.

## Things to Avoid

You should not write vague messages like "fix stuff" or "update". You should not include unnecessary detail.

## Additional Tips

Think about what a reviewer would want to know. Consider breaking large changes into multiple commits. Remember that the message is permanent.