Automated summary
Turns all unstaged working-tree changes into a set of atomic commits, after formatting the code and confirming the full check suite passes.
Strengths
- Runs `just fmt` and then the full `just` check suite first, stopping outright on a red build
- Proposes a grouped commit plan per file and waits for explicit approval before running `git add` / `git commit`
- Enforces a consistent message style (imperative, ~50 chars, 72-column body) matched against the last five commits
Limitations
- Assumes a `just`-based project with `fmt` and full-check recipes; not directly reusable elsewhere
- Does not repair a failing build itself — it halts and hands control back to the developer
- Never pushes, and does not handle ambiguous cases such as mixed-concern files or interdependent changes
When a working tree holds several unstaged changes that should become clean, reviewable commits on a `just`-driven project.
Avoid when the build is broken and won't be fixed right away, or when the project doesn't use `just`.
Security analysis
CautionThe skill uses Bash for legitimate formatting, build verification, and git commit workflows. There is no evidence of exfiltration, destructive filesystem commands, obfuscation, or safety-disabling behavior. However, invoking `just` executes repository-defined code, and committing changes writes to git history, so it warrants caution rather than a fully safe rating.
- •Runs `just` and `just fmt`, which execute project-defined recipes and can run arbitrary commands from the repository's Justfile.
- •Uses `git add` and `git commit`, which modify repository history; this is gated by an explicit approval step but still a write operation.
Examples
Commit all my unstaged changes.Split my working tree changes into logical atomic commits and show me the plan first.Format the code, make sure the checks pass, then commit all pending changes in atomic commits.name: commit-all description: Create atomic commits from all unstaged changes allowed-tools: Bash(just, just fmt, git status, git diff*, git add, git commit, git log)
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
- Group related changes into logical commits
- For each group, propose:
Commit 1: <message>
- path/to/file.clj (brief description of change)
Commit 2: <message>
- path/to/other.clj
- Ask "Ready to create these commits?" and wait for approval
- 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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/create-atomic-commits-mrwak9nj/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/create-atomic-commits-mrwak9nj' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-atomic-commits-mrwak9nj/download' --output '.skill-downloads/create-atomic-commits-mrwak9nj/SKILL.md.part' && mv '.skill-downloads/create-atomic-commits-mrwak9nj/SKILL.md.part' '.skill-downloads/create-atomic-commits-mrwak9nj/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(just, just fmt, git status, git diff*, git add, git commit, git log)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/create-atomic-commits-mrwak9nj/SKILL.md' && test -s '.skill-downloads/create-atomic-commits-mrwak9nj/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit-all' && cp -R '.skill-downloads/create-atomic-commits-mrwak9nj' '.claude/skills/commit-all'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/create-atomic-commits-mrwak9nj'openskills read 'create-atomic-commits-mrwak9nj'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/create-atomic-commits-mrwak9nj/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.