# Conventional Commits

> Conventional Commits

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

---


# Conventional Commits

Purpose: Format commits so release and review automation can reason about changes.

1. Choose one type: feat, fix, docs, test, refactor, chore, ci, build.
2. Add a short scope when useful.
3. Use imperative subject, 72 characters or less when practical.
4. Put evidence and breaking changes in the body.

Checklist:

- Type is valid.
- Subject names the change.
- Body includes verification when needed.
- No unrelated changes are hidden.

Positive example: `feat(agent): record prompt provenance on artifacts`.
Negative example: `updates`.

Failure modes: vague subjects, mixed unrelated work, missing breaking-change notes.