# Atomic Commits > Creates semantic atomic commits using Conventional Commits. Use always when committing changes, staging files, or when asked to commit code. Analyzes diffs, suggests scope, and can split changes into granular commits. - Skill: `majiayu000/atomic-commits-2` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds add majiayu000/atomic-commits-2` - Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/atomic-commits-2/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: majiayu000 (https://skillmd.com/u/majiayu000) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/majiayu000/atomic-commits-2 --- # Atomic Commits Creates well-structured, semantic commits following [Conventional Commits](https://www.conventionalcommits.org/) specification. Automatically analyzes changes and creates atomic, focused commits. ## Core Principles 1. **Atomic**: Each commit represents ONE logical change 2. **Semantic**: Type prefix describes the nature of the change 3. **Scoped**: Optional scope indicates the affected module/component 4. **Descriptive**: Message explains WHAT and WHY, not HOW ## Workflow ### Step 1: Analyze Changes Run these commands to understand the current state: ```bash git status git diff --staged git diff ``` ### Step 2: Identify Commit Types For each logical change, determine the appropriate type: | Type | When to Use | | ---------- | ------------------------------------------------------- | | `feat` | New feature for the user | | `fix` | Bug fix for the user | | `docs` | Documentation only changes | | `style` | Formatting, missing semicolons (no code change) | | `refactor` | Code change that neither fixes a bug nor adds a feature | | `perf` | Performance improvement | | `test` | Adding or fixing tests | | `build` | Build system or external dependencies | | `ci` | CI configuration files and scripts | | `chore` | Other changes that don't modify src or test files | | `revert` | Reverts a previous commit | ### Step 3: Determine Scope Analyze changed files to suggest scope: - `api/` → scope: `api` - `core/database.py` → scope: `db` - `agents/faq_agent/` → scope: `faq-agent` - `tests/` → scope: `tests` - Multiple areas → consider splitting into multiple commits ### Step 4: Create Atomic Commits If changes span multiple concerns, split them: ```bash git add -p # Stage hunks interactively (but explain to user) ``` Or stage specific files: ```bash git add git commit -m "(): " ``` ### Step 5: Validate Message Format Before committing, validate the message follows the pattern: ``` (): [optional body] [optional footer(s)] ``` Rules: - Type is required and lowercase - Scope is optional, lowercase, in parentheses - Description starts lowercase, no period at end - Max 72 characters for first line - Body wrapped at 72 characters - Breaking changes: add "!" after type/scope or "BREAKING CHANGE:" in footer - **NEVER add auto-generated labels** like "Generated with Claude Code", "Co-Authored-By", or any AI attribution - Commit messages must be clean and professional, as if written by the developer ## Commit Message Template ``` ():