Before we start, this guide assumes that you already have Claude Code installed and configured on your machine. If you haven’t set it up yet, you can find the official installation instructions here.

A clear and consistent commit message convention is essential for the maintainability and understanding of any project. In this post, I’ll show you how to use Claude Code, the AI assistant by Anthropic, to automate and improve the writing of your commit messages in just a few minutes.

1. Create custom /commit command

The first step is to tell Claude how you want your commit messages to be written. To do this, create a file named commit.md inside the .claude/commands folder at the root of your project.

In this file, you can define the guidelines or instructions that you want Claude to follow when generating commits. For example:

---
description: "Creates well-formatted commits with conventional commit messages and emoji"
allowed-tools:
  [
    "Bash(git add:*)",
    "Bash(git status:*)",
    "Bash(git commit:*)",
    "Bash(git diff:*)",
    "Bash(git log:*)",
  ]
---

# Claude Command: Commit

Creates well-formatted commits with conventional commit messages and emoji.

## Usage

```
/commit
/commit --no-verify
```

## Process

1. Check staged files, commit only staged files if any exist
2. Analyze diff for multiple logical changes
3. Suggest splitting if needed
4. Create commit with emoji conventional format
5. Husky handles pre-commit hooks automatically

## Commit Format

`<emoji> <type>: <description>`

**Types:**

- `feat`: New feature
- `fix`: Bug fix
- `docs`: Documentation
- `style`: Formatting
- `refactor`: Code restructuring
- `perf`: Performance
- `test`: Tests
- `chore`: Build/tools

**Rules:**

- Imperative mood ("add" not "added")
- First line <72 chars
- Atomic commits (single purpose)
- Split unrelated changes

## Emoji Map

✨ feat | 🐛 fix | 📝 docs | 💄 style | ♻️ refactor | ⚡ perf | ✅ test | 🔧 chore | 🚀 ci | 🚨 warnings | 🔒️ security | 🚚 move | 🏗️ architecture | ➕ add-dep | ➖ remove-dep | 🌱 seed | 🧑‍💻 dx | 🏷️ types | 👔 business | 🚸 ux | 🩹 minor-fix | 🥅 errors | 🔥 remove | 🎨 structure | 🚑️ hotfix | 🎉 init | 🔖 release | 🚧 wip | 💚 ci-fix | 📌 pin-deps | 👷 ci-build | 📈 analytics | ✏️ typos | ⏪️ revert | 📄 license | 💥 breaking | 🍱 assets | ♿️ accessibility | 💡 comments | 🗃️ db | 🔊 logs | 🔇 remove-logs | 🙈 gitignore | 📸 snapshots | ⚗️ experiment | 🚩 flags | 💫 animations | ⚰️ dead-code | 🦺 validation | ✈️ offline

## Split Criteria

Different concerns | Mixed types | File patterns | Large changes

## Options

`--no-verify`: Skip Husky hooks

## Notes

- Husky handles pre-commit checks
- Only commit staged files if any exist
- Analyze diff for splitting suggestions
- **NEVER add Claude signature to commits**

The clearer and more specific your instructions, the better the results from Claude.

2. Restart the Claude Code CLI

To make the new command appear in the Claude Code interface, you need to restart the CLI. Simply close and reopen your terminal or restart the Claude Code process if it was already active.

Once this is done, you'll see the new /commit command ready to use.

To prevent Claude Code from automatically including co-authors in the generated commits, you can disable this by adding the following line to the .claude/settings.local.json file:

{
  "includeCoAuthoredBy": false
}

This is especially useful if you work in a team or prefer to keep commits clean from additional annotations.

4. Use the /commit Command

With everything set up, you can now use the command directly in the Claude Code CLI by typing:

/commit

Claude will analyze the changes in your code and generate a commit message following the guidelines you defined in the commit.md file. If you're not satisfied with the result, you can always ask Claude to rephrase or adapt the message.

Conclusion

Integrating Claude Code into your workflow for writing commit messages not only saves you time but also helps maintain a high standard of quality and clarity in your change history. As with everything in development, the key lies in defining good rules and iterating until you find the format that best fits your team or project.

✅ Useful References:

Thanks for reading me 😊