القائمة
Use when the user asks to commit changes. Runs parallel git status/diff/log, drafts a conventional commit message, stages files by name, and handles pre-commit hook failures.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | quick-commit |
| description | Use when the user asks to commit changes. Runs parallel git status/diff/log, drafts a conventional commit message, stages files by name, and handles pre-commit hook failures. |
When the user asks to commit, follow this exact protocol.
git status # untracked and modified files (never use -uall)
git diff && git diff --staged # both staged and unstaged changes
git log --oneline -5 # recent commit style
feat: (new), fix: (bug), refactor:, test:, docs:, chore:.env, credentials.json, etc.)git add -A or git add .git commit -m "$(cat <<'EOF'
feat: add user authentication with JWT
EOF
)"
git status after commit to verify successIf a pre-commit hook fails:
--amend (that would modify the previous commit)--no-verify to skip hooks-i flag (interactive mode not supported)System design and architecture decisions. Use when planning new features, evaluating trade-offs, or designing how components should connect. Proposes 2-3 approaches and recommends one.
Smart commit workflow. Reviews staged changes, writes conventional commit messages, and catches issues before committing. Use when ready to commit work.
Quality review of completed work. Use after making changes and before claiming completion. Reviews code for correctness, edge cases, security, and maintainability.
Systematic debugging workflow. Use when diagnosing bugs, test failures, or unexpected behavior. Follows a rigorous reproduce → isolate → hypothesize → fix → verify cycle.
Systematic multi-agent research. Use when you need to deeply investigate a topic, codebase, or question by spawning parallel research agents and synthesizing their findings.
Deep code explanation. Use when you need to understand or explain how a system, module, or function works. Traces data flow, maps dependencies, and explains design decisions.