القائمة
Generate Git Commit Message (Gitmoji Convention)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Planning and execution protocol for multi-phase work in this Rust workspace. Use when the user asks for a plan, phased execution, acceptance criteria, scope control, QA evidence, or validation commands.
Refines Rust tests by removing irrelevant cases, consolidating redundant coverage, and enforcing repo testing rules (pretty_assertions + rstest + complete HTTP response assertions). Use when the user asks to clean up tests, remove redundancy, reduce flakiness/noise, or speed up CI.
| name | commit |
| description | Generate Git Commit Message (Gitmoji Convention) |
| disable-model-invocation | true |
Generate one commit message for staged changes using Gitmoji + Conventional Commits.
You MUST run these read-only git commands and use their outputs:
git rev-parse --abbrev-ref HEADgit diff --stagedgit status --porcelain=v1Return exactly two sections:
### Commit message### Next stepIf git diff --staged output is empty:
### Commit message, output a code block with exactly: NO_STAGED_CHANGES### Next step, ask to stage files and retry.If you cannot execute git commands or do not have their outputs:
### Commit message, output a code block with exactly: NEEDS_GIT_OUTPUT### Next step, ask the user to paste outputs for the three commands above.Pick the dominant change; do not combine types in the title.
(context) from branchFirst match wins:
ABC-123, use (ABC-123).feature/<scope> / fix/<scope> / chore/<scope>, use (<scope>).(context) (do not invent).Normalize <scope>:
feature/, bugfix/, hotfix/<emoji> <type>: (context) <imperative summary>
(context) optional; if present, exactly one pair of parentheses.After one blank line, include 2–6 bullets:
- .NO_STAGED_CHANGES.git add, git commit, git push, git checkout, git reset, git rebase).