# Git Conventional Naming > Implementing the Conventional Commits specification for structured and machine-readable commit messages. Use when this capability is needed. - Skill: `tomevault-io/git-conventional-naming` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/git-conventional-naming` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-conventional-naming/raw - Safety review: pending - 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/git-conventional-naming --- # Git Conventional Naming Standardizing commit messages makes history searchable and allows for automated changelog generation. ## Format `[optional scope]: ` ## Common Types - **`feat`**: A new feature for the user. - **`fix`**: A bug fix for the user. - **`docs`**: Documentation only changes. - **`style`**: Changes that do not affect the meaning of the code (white-space, formatting). - **`refactor`**: A code change that neither fixes a bug nor adds a feature. - **`perf`**: A code change that improves performance. - **`test`**: Adding missing tests or correcting existing tests. - **`chore`**: Changes to the build process or auxiliary tools and libraries. ## Examples - `feat(api): add user authentication endpoint` - `fix(ui): resolve alignment issue on mobile header` - `docs: update deployment instructions` ## Value Automatically generate release notes and version numbers based on the commit history. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jcorpac) — claim your Tome and manage your conversions.