# Conventional Commit > Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification. - Skill: `adobe/conventional-commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add adobe/conventional-commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/adobe/conventional-commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MIT - Author: Adobe (https://skillmd.com/u/adobe) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/adobe/conventional-commit --- # Conventional Commit Messages Follow these conventions when creating commits. ## Mindset You are writing for the next person who reads this commit log, not for yourself. Clarity and consistency matter more than brevity. Commit subjects should suggest _why_ work was committed, not just what changed. ## Prerequisites Before committing, ensure you're working on a feature branch, not the main branch. ```bash # Check current branch git branch --show-current ``` If you're on `main` or `master`, create a new branch first: ```bash # Create and switch to a new branch git checkout -b / ``` Branch naming should follow the pattern: `/` where type matches the commit type (e.g., `feat/add-user-auth`, `fix/null-pointer-error`, `refactor/extract-validation`). ## Format ``` ():