# Commit > Create well-structured commit messages following Conventional Commits format. Use when committing code changes, writing commit messages, or formatting git history. - Skill: `steveclarke/commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add steveclarke/commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/steveclarke/commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: steveclarke (https://skillmd.com/u/steveclarke) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/steveclarke/commit --- # Commit Messages Follow these conventions when creating commits. ## Prerequisites Before committing, ensure you're working on a feature branch, not the master branch. ```bash # Check current branch git branch --show-current ``` If you're on `master`, create a new branch first: ```bash # Create and switch to a new branch git checkout -b / ``` ## Branch Naming Branch names follow the pattern: ``` {type}/{brief-description} ``` For work tied to a feature epic, include the feature ID: ``` {type}/{feature-id}-{brief-description} ``` **Examples:** - `feat/add-user-auth` - Adding authentication - `feat/FT050-workflow-automation` - Feature epic work - `fix/resolve-link-validation` - Bug fix - `docs/workflow-guide` - Documentation - `chore/update-ruby-version` - Dependencies ## Commit Format ``` :