Conventional Commits

Conventional Commits

onfire7777 6214593 720 B Updated

File contents

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.

onfire7777/five-agent-dev-team/tree/main/packages/agents/skills/shared/conventional-commits commit 6214593217

Frequently asked questions

npx skillmds@latest add onfire7777/conventional-commits