Automated summary
Analyzes uncommitted changes in a repository and creates atomic commits that follow the project's conventions, after the user approves a proposed plan.
Strengths
- Splits changes into atomic commits using explicit atomicity rules rather than a flat list of files
- Reads project conventions and the active issue so commits can reference a ticket via Closes #N or Part of #N
- Presents a detailed plan and waits for confirmation before running any git add or git commit
- Optionally hands off to /open-pr to push the branch and open the pull request
Limitations
- Relies on repository-specific configuration files (.claude/rules/code-conventions.md, atomicity-rules.md, .claude/current-issue) that must exist or be adapted
- Issue lookup depends on the gh CLI and silently degrades if it is not authenticated
- Does not cover advanced git operations such as rebase, revert, or conflict resolution
Use it when a batch of pending changes needs to become clean, well-scoped commits without hand-writing the messages.
Avoid it on repositories without defined conventions, or for git tasks other than creating commits (rebase, revert, conflict resolution).
Security analysis
CautionThe skill is a fairly conservative commit workflow: it diagnoses, groups changes into atomic commits, presents a plan and explicitly waits for confirmation before staging/committing, and it never pushes without an extra opt-in. It uses git and gh CLI for exactly their legitimate purposes: no destructive commands, no network exfiltration, no obfuscated payloads, no secret handling. The only real concerns are the inherent power of git commit plus the unquoted `$(cat .claude/current-issue)` substitution and reliance on repo-local rule files, which is why caution rather than safe is appropriate.
- •Runs shell commands (git status/diff/add/commit, gh issue view) that mutate the repository — intended purpose, but still powerful tooling that should be gated by the confirmation step
- •Unquoted command substitution `gh issue view $(cat .claude/current-issue)` can misbehave if that file contains unexpected/whitespace content; minor injection/robustness concern
- •Depends on external files not shipped here (./atomicity-rules.md, .claude/rules/code-conventions.md, .claude/current-issue) so behavior is partly determined by unreviewed content in the target repo
- •Optional follow-on `/open-pr` performs push and PR creation — but only after explicitly asking the user
Examples
Commit my current changes as atomic commits following the project conventions.Analisa as mudanças não-commitadas e propõe um plano de commits atômicos antes de executar qualquer coisa.Stage and commit this refactor, and link the commits to the current active issue.name: commit description: Analisa mudanças não-commitadas e realiza commits atômicos seguindo as convenções do projeto. Use when the user wants to commit changes, stage files, or create a structured commit message. $ARGUMENTS
Commit
Workflow
1. Diagnosticar
git status
git diff --stat HEAD
Se a working tree estiver limpa, informe o usuário e pare.
2. Ler convenções
atomicity-rules.md— tipos, escopos, regras de atomicidade.claude/rules/code-conventions.md— convenções de código do projeto
3. Identificar issue ativa
cat .claude/current-issue 2>/dev/null || echo "(nenhuma)"
gh issue view $(cat .claude/current-issue) --json number,title,body,labels 2>/dev/null
4. Inspecionar mudanças
git diff # não-staged
git diff --cached # staged
git ls-files --others --exclude-standard # untracked
Leia arquivos novos relevantes com Read para entender o que fazem.
5. Agrupar em commits atômicos
Aplique as regras de atomicidade. Regra de ouro: se precisar de mais de uma frase para descrever o que foi feito (não o porquê), divida o commit.
6. Propor plano — aguardar confirmação
Plano de commits (N commits):
1. tipo(escopo): descrição curta
Arquivos: path/arquivo1.py, path/arquivo2.py
Corpo: [porquê da mudança, se necessário]
Se houver issue ativa, o último commit relevante deve referenciar no rodapé (Closes #N ou Part of #N). Aguardar confirmação antes de executar.
7. Executar após confirmação
git add caminho/arquivo1 caminho/arquivo2
git commit -m "tipo(escopo): descrição
Corpo opcional (wrap a 72 chars).
Closes #N"
git log --oneline -1 # confirmar cada commit
8. Resumo final
git log --oneline -N
Perguntar se deseja abrir o PR agora via /open-pr (que faz o push, cria o PR e
move as issues para In review). Se a resposta for não, parar aqui — sem push.
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/atomic-commit-mrwakeqy/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/atomic-commit-mrwakeqy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/atomic-commit-mrwakeqy/download' --output '.skill-downloads/atomic-commit-mrwakeqy/SKILL.md.part' && mv '.skill-downloads/atomic-commit-mrwakeqy/SKILL.md.part' '.skill-downloads/atomic-commit-mrwakeqy/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.
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/atomic-commit-mrwakeqy/SKILL.md' && test -s '.skill-downloads/atomic-commit-mrwakeqy/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/atomic-commit-mrwakeqy' '.claude/skills/commit'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/atomic-commit-mrwakeqy'openskills read 'atomic-commit-mrwakeqy'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/atomic-commit-mrwakeqy/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.