How do I install the Git Committer Atomic skill?

Run npx skillmds@latest add majiayu000/git-committer-atomic in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Git Committer Atomic skill do?

Plan and create atomic commits ordered by dependencies It is listed under Coding & Dev Tools on SkillMD.

Is Git Committer Atomic safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Committer Atomic?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Committer Atomic free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Committer Atomic?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Committer Atomic by majiayu000 — Agent Skill

Name: Git Committer Atomic
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Git Committer Atomic Skill

Overview

Split changes into atomic commits ordered by dependency.

Usage

/git-committer-atomic

Identity

Role: Git Operations Specialist Objective: Break down the current set of changes into atomic, logical commits, ensuring dependencies are committed before consumers.

Context

You are working in a dirty git state. Your goal is to reach a clean git state (git status clean) by creating a series of well-structured commits.

Workflow Rules

1. Analysis Phase

Run git status --porcelain to see all changes.
Analyze dependencies between changed files.
Dependency Hierarchy (Commit in this order):
1. Infrastructure: Config files, build scripts, strict types (tsconfig.json, package.json).
2. Core/Utils: Shared libraries, helper functions, base classes.
3. Domain/Models: Database schemas, entity definitions, DTOs.
4. Services: Business logic, API handlers.
5. Features/UI: React components, pages, routes.
6. Tests: Unit and integration tests (can be committed with features if tight, but often separate).

2. Execution Loop

While git status is not clean:

Identify the next logical group of files based on the hierarchy above.
Stage these files: git add <file1> <file2>.
- If a file contains multiple logical changes (e.g., a fix AND a feature), instruct the user to use git add -p or split it yourself if capable.
Verify (Mental Check): Does this commit compile/make sense on its own?
Commit: Generate a conventional commit message (ref: git-commit-conventional).
- Format: type(scope): description
- Example: feat(utils): add date formatting helper
Repeat.

Constraints

Atomic: Each commit must do one thing.
Buildable: Avoid leaving the repo in a broken state between commits if possible.
No "WIP": Do not create "Work in progress" commits unless explicitly asked.

Agent Compatibility

Claude: Use strict ordering.
Cursor: Focus on file grouping logic.
Gemini: verification of dependency graph logic.

Outputs

Ordered list of atomic commits with rationale.

Related Skills

/git-commit-conventional - Message formatting

---name: git-committer-atomicdescription: Plan and create atomic commits ordered by dependencies--- # Git Committer Atomic Skill ## Overview Split changes into atomic commits ordered by dependency. ## Usage ``` /git-committer-atomic ``` ## Identity **Role**: Git Operations Specialist **Objective**: Break down the current set of changes into atomic, logical commits, ensuring dependencies are committed before consumers. ## Context You are working in a dirty git state. Your goal is to reach a clean git state (`git status` clean) by creating a series of well-structured commits. ## Workflow Rules ### 1. Analysis Phase - Run `git status --porcelain` to see all changes. - Analyze dependencies between changed files. - **Dependency Hierarchy** (Commit in this order): 1. **Infrastructure**: Config files, build scripts, strict types (`tsconfig.json`, `package.json`). 2. **Core/Utils**: Shared libraries, helper functions, base classes. 3. **Domain/Models**: Database schemas, entity definitions, DTOs. 4. **Services**: Business logic, API handlers. 5. **Features/UI**: React components, pages, routes. 6. **Tests**: Unit and integration tests (can be committed with features if tight, but often separate). ### 2. Execution Loop While `git status` is not clean: 1. **Identify** the next logical group of files based on the hierarchy above. 2. **Stage** these files: `git add <file1> <file2>`. - If a file contains multiple logical changes (e.g., a fix AND a feature), instruct the user to use `git add -p` or split it yourself if capable. 3. **Verify** (Mental Check): Does this commit compile/make sense on its own? 4. **Commit**: Generate a conventional commit message (ref: `git-commit-conventional`). - Format: `type(scope): description` - Example: `feat(utils): add date formatting helper` 5. **Repeat**. ## Constraints - **Atomic**: Each commit must do one thing. - **Buildable**: Avoid leaving the repo in a broken state between commits if possible. - **No "WIP"**: Do not create "Work in progress" commits unless explicitly asked. ## Agent Compatibility - **Claude**: Use strict ordering. - **Cursor**: Focus on file grouping logic. - **Gemini**: verification of dependency graph logic. ## Outputs - Ordered list of atomic commits with rationale. ## Related Skills - `/git-commit-conventional` - Message formatting

Frequently asked questions

Git Committer Atomic