القائمة
Create multiple git commits, one per concern, from changes in the working tree
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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
Create a git commit
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.
| name | commit-multiple |
| description | Create multiple git commits, one per concern, from changes in the working tree |
| allowed-tools | Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git reset HEAD:*), Bash(git diff:*), Bash(if git diff --staged --quiet; then git diff; else git diff --staged; fi) |
git statusif git diff --staged --quiet; then git diff; else git diff --staged; figit branch --show-currentgit log --oneline -10 2>/dev/null || echo "No commits yet"$ARGUMENTS
Single-line Conventional Commit:
Group all working-tree changes (staged and unstaged) by logical concern — application, feature, or purpose. Each group becomes one commit.
Steps:
git reset HEAD to unstage (only if anything is staged)git add the files (or hunks) for that group
b. git commit -m "message" — single-line, no heredocs or $()git status to confirm the tree is cleanIf a single file contains hunks for truly distinct concerns (e.g. different commit types or scopes), split them across commits; otherwise keep the whole file in its most relevant commit.