القائمة
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help commiting code, writing commit messages, or reviewing staged changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Grilling and design session that challenges your plan against the existing codebase, domain model, and documented decisions; sharpens terminology; updates documentation (CONTEXT.md, design docs) inline as decisions crystallize; and produces committable implementation plans. Use when user wants to stress-test, design, or plan a feature against their project's language and documented decisions.
Grilling and design session that challenges your plan against the existing codebase, domain model, and documented decisions; sharpens terminology; updates documentation (CONTEXT.md, design docs) inline as decisions crystallize; and produces committable implementation plans. Use when user wants to stress-test, design, or plan a feature against their project's language and documented decisions.
Capture polished screenshots of terminal applications and TUIs. Use before terminal-control when the user wants a terminal screenshot or live TUI state documented.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets, and resolve them one at a time until the way to the destination is clear.
Review local docs and create a git commit or pull request. Use when committing changes with documentation review, or opening a PR.
Use at the end of a unit of work, before commit or PR, to verify related documentation matches the new state
| name | commit-msg |
| description | Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help commiting code, writing commit messages, or reviewing staged changes. |
Commit messages are trust artifacts. A well-written commit should give the reader enough context to decide whether they need to review the code at all. Capture intent, decisions, and verification — not just what files changed.
Before drafting the message, collect:
# What's staged
git diff --staged --stat
git diff --staged
# Recent commits for tone and convention
git log --oneline -5
Read the diff carefully. Understand why the change was made, not just what changed. If you made the changes yourself, you already have this context — use it.
<type>(<scope>): <summary>
Why: <problem solved or request fulfilled>
Approach: <what was done and key decisions made>
Verified: <how correctness was confirmed>
[Tradeoffs: <alternatives considered, things intentionally left out>]
[Breaking: <what breaks and migration path>]
Follow conventional commits. Keep the summary under 50 characters, imperative mood.
Types: feat, fix, docs, style, refactor, test, chore
One or two sentences explaining the motivation. What was broken, missing, or requested? This should make sense to someone who wasn't in the conversation where the work was discussed.
What you did and, critically, why you did it that way. Include:
This is where agent context gets preserved. If you chose approach A over approach B, say so. That reasoning exists in your working memory right now and will be lost after the session ends.
How you know the change is correct. Be specific:
If verification was limited, say that too: "No existing test suite — verified by running the script against sample input." Honest verification is more useful than vague confidence.
Include when you made a deliberate choice between reasonable alternatives. Skip for straightforward changes where there was one obvious path.
If the change breaks existing behavior, state what breaks and how to migrate. Use the ! suffix in the header too: feat(api)!: restructure response format
Match message depth to change significance. A dependency bump doesn't need a Tradeoffs section. A major architectural change deserves every section plus maybe an ADR. Use judgment.
git commit -m "<header>" -m "<body>"
For longer messages, prefer writing to a temp file:
cat > /tmp/commit-msg.txt << 'EOF'
<full message>
EOF
git commit -F /tmp/commit-msg.txt
Before committing: