atomic-commit

星标15

分支0

更新时间2026年2月16日 06:32

Split changes into atomic commits with clean staging and concise messages. Use when the user asks for "atomic commits", "split this into commits", "commit hygiene", or wants guidance on separating changes into reviewable pieces.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

chasebuild

chasebuild/fuelcheck-cli

打开 GitHub 仓库查看创作者相关仓库

下载

Atomic Commit

Use this skill to split a working tree into small, logical commits that are easy to review.

Read First

If repo-specific PR or commit workflow docs exist, follow them.
For OpenClaw-style guidance, see references/openclaw-pr-workflow.md.

Workflow

Inventory changes.

Run git status -sb and git diff.
Group changes by intent (feature, fix, refactor, formatting, docs, tests).

Split by intent.

Separate behavior changes from formatting.
Split refactors from functional changes when possible.
Keep tests with the change they validate.

Stage atomically.

Use git add -p to stage only the hunks for the current commit.
Use git add -N to partially stage new files.
Re-check with git diff --staged before committing.

Commit message guidance.

Keep messages concise, present-tense, action-oriented.
Use a small scope prefix when helpful: <area>: <action>.

Verify cleanliness.

After each commit, ensure the staged diff is empty and remaining changes match the next commit group.

Ask before risky splits.

If a change is tightly coupled or splitting would create broken intermediate states, ask before proceeding.

Output

After splitting, report:

Commit list (hash + message)
What remains uncommitted

同仓库更多 Skills

同仓库

rust-skills

chasebuild/fuelcheck-cli

Comprehensive Rust coding guidelines with 179 rules across 14 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Invoke with /rust-skills.

2026-02-1615

auto-git-commit

chasebuild/fuelcheck-cli

Automate git commits with correct staging and messages. Use when the user asks to "commit my changes", "auto commit", "stage and commit", "commit everything", or wants commits created on their behalf. Covers deciding whether to split changes, staging with git add -p, and producing concise commit messages.

2026-02-1615

rust-skills

chasebuild/fuelcheck-cli

2026-02-1615

name	atomic-commit
description	Split changes into atomic commits with clean staging and concise messages. Use when the user asks for "atomic commits", "split this into commits", "commit hygiene", or wants guidance on separating changes into reviewable pieces.

Atomic Commit

Use this skill to split a working tree into small, logical commits that are easy to review.

Read First

If repo-specific PR or commit workflow docs exist, follow them.
For OpenClaw-style guidance, see references/openclaw-pr-workflow.md.

Workflow

Inventory changes.

Run git status -sb and git diff.
Group changes by intent (feature, fix, refactor, formatting, docs, tests).

Split by intent.

Separate behavior changes from formatting.
Split refactors from functional changes when possible.
Keep tests with the change they validate.

Stage atomically.

Use git add -p to stage only the hunks for the current commit.
Use git add -N to partially stage new files.
Re-check with git diff --staged before committing.

Commit message guidance.

Keep messages concise, present-tense, action-oriented.
Use a small scope prefix when helpful: <area>: <action>.

Verify cleanliness.

After each commit, ensure the staged diff is empty and remaining changes match the next commit group.

Ask before risky splits.

If a change is tightly coupled or splitting would create broken intermediate states, ask before proceeding.

Output

After splitting, report:

Commit list (hash + message)
What remains uncommitted