# Atomic Git Commit

> Interactive workflow to review changes, split them into logical groups, and create atomic conventional commits. Replaces 'git commit -m' with a thoughtful process. Use when this capability is needed.

- Skill: `tomevault-io/atomic-git-commit` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/atomic-git-commit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/atomic-git-commit/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/atomic-git-commit

---


# Atomic Git Commit Workflow

This skill guides you through the process of reviewing uncommitted changes, grouping them logically, and creating atomic commits following Conventional Commits standards.

## When to Use

- When the user asks to "commit changes", "review and commit", "save work".
- When you have completed a task and have modified multiple files.
- **Do NOT use** for "fire and forget" saves (use `git-pushing` for that). This is for *thoughtful* committing.

## Workflow

### 1. Analyze State

Run the following checks to understand what has changed:

```bash
git status
git diff --stat
```

### 2. Group Changes

**CRITICAL**: Do not just `git add .` unless all changes are strictly related to a single atomic unit of work.

- **Feat**: New features.
- **Fix**: Bug fixes.
- **Chore**: Maintenance, config, `.agent` updates.
- **Docs**: Documentation changes.

*Interactive Thought Process:*
"I see changes in `backend/` and `frontend/`. Are they part of the same feature? If yes, commit together. If they are separate fixes, split them."

### 3. Commit

For each logical group:

1. Stage specific files: `git add <file1> <file2>`
2. Commit with conventional message:

   ```bash
   git commit -m "<type>(<scope>): <description>"
   ```

**Types**: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`.

### 4. Verify

- Ensure no unintended files (secrets, `.env`, temporary logs) are committed.
- Check `git status` one last time.

## Local Overrides

Check if `.agent/local-rules/commit-conventions.md` exists for project-specific commit rules.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/maraxen) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->