CO

commit-all

Helps developers bundle changes into logical, atomic commits after running automated formatting and verification.

Install

mkdir -p .claude/skills/commit-all && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12077" && unzip -o skill.zip -d .claude/skills/commit-all && rm skill.zip

Installs to .claude/skills/commit-all

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create atomic commits from all unstaged changes
47 charsno explicit “when” trigger
Beginner

Key capabilities

  • Format code using `just fmt`.
  • Verify the build passes using `just` before committing.
  • Group related unstaged changes into logical commits.
  • Propose commit messages and associated files to the user.
  • Add files and commit them with the approved messages.

How it works

The skill formats code, verifies the build, then interactively helps the user group unstaged changes into atomic commits with conventional messages.

Inputs & outputs

You give it
Unstaged changes in the repository
You get back
Atomic commits created from the unstaged changes

When to use commit-all

  • Creating atomic commits
  • Preparing code for final commit
  • Organizing changes before push

About this skill

Commit All Unstaged Changes

Create atomic commits from all unstaged changes.

Step 1: Format Code

!just fmt

Step 2: Verify Green Build

Run the full check suite before doing anything else. This catches broken code before it gets committed.

!just

If this fails, stop and fix the issues first. Do not proceed to commit planning with a failing build. Re-run just after fixing until it passes.

Current State

!git status --short

!git diff --stat

Process

  1. Group related changes into logical commits
  2. For each group, propose:
Commit 1: <message>
  - path/to/file.clj (brief description of change)

Commit 2: <message>
  - path/to/other.clj
  1. Ask "Ready to create these commits?" and wait for approval
  2. After approval, for each commit:
    • git add <files>
    • git commit -m "<message>"

Commit Style

  • Summary line: imperative mood, capitalised, no trailing period, ~50 chars
  • Blank line, then optional body wrapped at 72 chars
  • Body explains why, not how — only include when it adds value
  • No Co-Authored-By trailers

Match recent style:

!git log --oneline -5

$ARGUMENTS

When not to use it

  • When the build is failing.
  • When the user does not want to create atomic commits.
  • When the user wants to commit all changes in a single, large commit.

Limitations

  • Requires `just fmt` and `just` commands to be available.
  • Requires user approval for commit creation.
  • Does not automatically fix failing builds.

How it compares

This skill structures the commit process by enforcing formatting, build verification, and atomic commit creation, unlike manually staging and committing changes.

Compared to similar skills

commit-all side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
commit-all (this skill)05moReviewBeginner
resolve-conflicts818moReviewIntermediate
openspec-onboard106moReviewBeginner
codex-cli-bridge99moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry