Agent skill

Commit Atomic

Group staged changes into atomic commits with commitizen convention

MITAuto-check passedDevelopment

Install Commit Atomic

skills CLI

$ npx skills add jellydn/my-ai-tools --skill commit-atomic -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools commit-atomic --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/commit-atomic .claude/skills/commit-atomic && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "commit-atomic" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/commit-atomic into .claude/skills/commit-atomic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-atomic", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/jellydn/my-ai-tools/tree/main/skills/commit-atomic

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill commit-atomic -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools commit-atomic --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/commit-atomic .agents/skills/commit-atomic && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "commit-atomic" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/commit-atomic into .agents/skills/commit-atomic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-atomic", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill commit-atomic -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools commit-atomic --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/commit-atomic .cursor/skills/commit-atomic && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "commit-atomic" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/commit-atomic into .cursor/skills/commit-atomic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-atomic", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/jellydn/my-ai-tools.git --path skills/commit-atomic

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill commit-atomic -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools commit-atomic --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/commit-atomic .gemini/skills/commit-atomic && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "commit-atomic" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/commit-atomic into .gemini/skills/commit-atomic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-atomic", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install jellydn/my-ai-tools commit-atomic

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add jellydn/my-ai-tools --skill commit-atomic -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/commit-atomic .github/skills/commit-atomic && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "commit-atomic" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/commit-atomic into .github/skills/commit-atomic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-atomic", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill commit-atomic -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools commit-atomic --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/commit-atomic .opencode/skills/commit-atomic && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "commit-atomic" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/commit-atomic into .opencode/skills/commit-atomic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-atomic", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: commit-atomic
GitHub stars: 123
Token cost: ~1.1k tokens
SKILL.md length: 354 words
Files: 1
Skills in repo: 35
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Group staged changes into atomic commits with commitizen convention

Works in 5 steps: Inspect the current changes → Group changes logically → Stage each group intentionally → …
Development work in your project
SKILL.md covers Usage, Process and Rules
Calls git

What it does

Commit Atomic is an agent skill from jellydn/my-ai-tools. Group staged changes into atomic commits with commitizen convention

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi

It sits in Development. It works with Git. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/commit-atomic”

Requirements

Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Inspect the current changes
Group changes logically
Stage each group intentionally
Commit each group with a commitizen message
Verify after each commit

What it can do on your machine

Read from SKILL.md and the folder at commit 163951e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
cline, claude, opencode, amp, codex, gemini, cursor, pi
From compatibility in the SKILL.md frontmatter.

Context cost

Commit Atomic loads about 1.1k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 354 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~20
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jellydn/my-ai-tools at commit 163951e, republished under its MIT licence (© jellydn). 354 words, ~1,058 tokens.

Download SKILL.mdSave it as .claude/skills/commit-atomic/SKILL.md (or your agent's skills folder).

name: commit-atomic
description: Group staged changes into atomic commits with commitizen convention
compatibility: cline, claude, opencode, amp, codex, gemini, cursor, pi
license: MIT
hint: Use when committing staged changes as focused, atomic commits grouped by logical change
user-invocable: true
metadata.audience: all
metadata.workflow: git

Atomic Commit with Logical Grouping

Create atomic commits by logically grouping changes following the commitizen/conventional commits convention. Each commit should represent one logical change with a clear, informative message explaining the what and why.

Usage

bash

/commit-atomic

Process

1. Inspect the current changes

bash

git status
git diff --staged
git diff

Review all modified, added, and deleted files to understand the full scope of changes.

2. Group changes logically

Analyze the changes and group them into logical, independent units. Each group should:

Address a single concern or feature
Be independently understandable
Not break the build or tests on its own
Follow the dependency order (low-level to high-level)

Grouping strategies:

By feature or concern (e.g., authentication, UI, database)
By type (e.g., refactoring, bug fix, new feature)
By layer (e.g., model, service, controller)

3. Stage each group intentionally

Stage files explicitly with git add <path>. Avoid git add -A or git add --all:

bash

# Stage specific files
git add <file1> <file2>

# Stage specific hunks interactively
git add -p <file>

# Verify what is staged before committing
git diff --staged

4. Commit each group with a commitizen message

Follow the commitizen conventional commits format:

text

<type>(<scope>): <subject>

[optional body]

[optional footer]

Types:

Type	When to use
`feat`	A new feature
`fix`	A bug fix
`docs`	Documentation only changes
`style`	Formatting, missing semicolons (no code logic change)
`refactor`	Code change that is neither a fix nor a feature
`perf`	A code change that improves performance
`test`	Adding or fixing tests
`chore`	Build process or auxiliary tool changes
`ci`	CI configuration changes
`build`	Changes that affect the build system or dependencies
`revert`	Reverts a previous commit

Show full SKILL.md (126 more words)Show less

Writing good commit messages:

Subject line: Imperative mood, max 72 characters, no period at end
Body (optional): Explain the why, not just the what; wrap at 72 characters
Footer (optional): Reference issues (Closes #123), breaking changes (BREAKING CHANGE: ...)

Examples:

feat(auth): add JWT refresh token support

Refresh tokens allow users to stay logged in without re-authenticating.
This reduces friction for long-running sessions.

Closes #42

fix(api): handle null response from external service

The external API occasionally returns null for optional fields.
Previously this caused an unhandled TypeError at runtime.

text

refactor(utils): extract date formatting into shared helper

Consolidates duplicate date formatting logic spread across three
modules into a single reusable function.

5. Verify after each commit

bash

git log --oneline -5
git status

Ensure the working tree is clean after all logical groups are committed.

Rules

❌ Prefer git add <path> over git add -A or git add --all
❌ Keep each commit focused on one logical change
✅ Stage files explicitly with git add <file> or git add -p
✅ Verify staged changes with git diff --staged before committing
✅ Write messages in imperative mood ("add feature" not "added feature")
✅ Explain the why in the commit body when the change is non-obvious
✅ Keep each commit independently buildable and testable

Files

Just SKILL.md in skills/commit-atomic of jellydn/my-ai-tools.

Open the folder on GitHubat commit 163951e

Compare with similar skills

Commit Atomic next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit Atomic compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Commit Atomic this skilljellydn/my-ai-tools	123	—	~1.1k	Automated safety check: Pass	MIT	today
Finishing a Development Branchobra/superpowers	296k	5 repos	~1.9k	Automated safety check: Pass	MIT	today
Code Review ChecklistshareAI-lab/learn-claude-code	78k	5 repos	~1.1k	Automated safety check: Pass	MIT	9 days ago
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything	85k	1 repos	~1.2k	Automated safety check: Pass	MIT	yesterday
Code Design Rationale Investigatorcursor/plugins	10k	9 repos	~2.6k	Automated safety check: Pass	None	yesterday
Understand Diff AnalysisEgonex-AI/Understand-Anything	85k	1 repos	~1.4k	Automated safety check: Pass	MIT	yesterday

Similar skills

Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
296k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 5 repos~1.1k tokens
DevelopmentAuto-check passed
Codebase Knowledge Graph Q&A
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
85k GitHub starsUsed in 1 repo~1.2k tokens
DevelopmentAuto-check passed
Code Design Rationale Investigator
cursor/plugins
Official
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
10k GitHub starsUsed in 9 repos~2.6k tokens
DevelopmentAuto-check passed
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
85k GitHub starsUsed in 1 repo~1.4k tokens
DevelopmentAuto-check passed
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
85k GitHub starsUsed in 1 repo~1.3k tokens
DevelopmentAuto-check passed

Questions about Commit Atomic

What does Commit Atomic do?

Group staged changes into atomic commits with commitizen convention. Commit Atomic is an agent skill from jellydn/my-ai-tools.

When should I use Commit Atomic?

Commit Atomic fits situations like: development work in your project.

How do I install Commit Atomic in Claude Code?

Run `npx skills add jellydn/my-ai-tools --skill commit-atomic -a claude-code`. Or copy the skill folder (skills/commit-atomic in jellydn/my-ai-tools) into .claude/skills/commit-atomic in your project. Claude Code loads it when a task matches its description.

How do I install Commit Atomic in Codex?

Run `npx skills add jellydn/my-ai-tools --skill commit-atomic -a codex`. Or copy the skill folder (skills/commit-atomic in jellydn/my-ai-tools) into .agents/skills/commit-atomic in your project. Codex loads it when a task matches its description.

Can I use Commit Atomic in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jellydn/my-ai-tools --skill commit-atomic -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-atomic, .gemini/skills/commit-atomic, .github/skills/commit-atomic and .opencode/skills/commit-atomic in your project.

What does Commit Atomic need to run?

Going by SKILL.md and its folder, Commit Atomic needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.

Does Commit Atomic access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit Atomic safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Commit Atomic use?

Commit Atomic is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit Atomic use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit Atomic?

Skills that share tags, products or a category with Commit Atomic: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Atomic?

jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.

Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Commit Atomic

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Atomic Commit with Logical Grouping

Usage

Process

1. Inspect the current changes

2. Group changes logically

3. Stage each group intentionally

4. Commit each group with a commitizen message

5. Verify after each commit

Rules

Files

Compare with similar skills

Similar skills

More from jellydn/my-ai-tools

Related

Questions about Commit Atomic