# Write Commit Message

> Use when creating git commits to ensure consistent, clear commit messages following conventional commits format.

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

---


# Write Commit Message

Create git commit messages following the Conventional Commits format.

## Template

See `templates/commit-message.md` for the full template structure, format rules, and examples.

## Quick Reference

**Format**:
```
<type>(<scope>): <subject>

[optional body]

[optional footer]
```

**Common Types**: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`

**Key Rules**:
- Subject < 72 characters
- Use imperative mood ("add" not "added")
- No period at end of subject
- Body explains what and why, not how

## Integration with Git Workflow

When user asks to commit or you're following git workflow:

1. Run `git status` and `git diff` to see changes
2. Analyze the nature of changes
3. Draft commit message following format
4. Use heredoc for proper formatting:

```bash
git commit -m "$(cat <<'EOF'
feat(auth): add JWT token refresh

Implements automatic token refresh mechanism.
EOF
)"
```

## Benefits

- Clear, scannable git history
- Semantic versioning compatibility
- Automatic changelog generation
- Easy to search and filter commits

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/eveld) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->