Menu
Create a git commit
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
After a code change, test it end-to-end (bash, browser, or computer use — whichever fits) and then run `/simplify` to review and clean up the changed code. Use to confirm a change works and is tidy before wrapping up.
Create a git commit and push it
Ask the user for maximum clarifications before acting on a prompt. Use when the user wants to ensure all ambiguity is resolved before work begins.
Write or refresh a README that earns the reader's attention — short, honest, with a real visual. Tailored to the project type.
Greenfield product spec for an empty repo. Clarifies scope, then challenges the idea — checking whether it already exists and whether the pain is real — before writing a concise spec.md.
Create multiple git commits, one per concern, from changes in the working tree, then push them
| name | commit |
| description | Create a git commit |
| allowed-tools | Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git diff:*) |
| disable-model-invocation | true |
git statusgit diff --stagedgit diffgit branch --show-currentgit log --oneline -10 2>/dev/null || echo "No commits yet"$ARGUMENTS
Pick exactly one of these scopes based on the current conversation:
Conversation has context (you have made or discussed edits earlier in this conversation):
commit ONLY the files that were touched/discussed in this conversation.
Do NOT include unrelated working-tree changes — leave them untouched (staged or unstaged).
Mechanics: git add <paths> (needed so untracked conversation files become known), then
git commit -m "..." -- <paths>. The trailing pathspec is required — it makes the commit
ignore any unrelated entries already in the index. Never use git add -A / git add ..
Whole-file scope is fine: if a conversation file also has unrelated local hunks, they ride along.
First message, something is staged: commit ONLY what is already staged. Do not add anything.
First message, nothing staged: commit everything in the working tree (git add -A).
If the working tree is also clean (nothing to commit at all), stop and tell the user — do not make an empty commit.
If unsure whether a change belongs to the conversation, leave it out.
Single-line Conventional Commit:
$() command substitution.