القائمة
Write a Conventional Commit message from a description of changes. Lead with WHY, not WHAT.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Compose a 5-7-5 syllable haiku on any topic. Bias toward concrete imagery over abstraction.
At the end of a session, decide what's worth remembering and what's worth turning into a skill. Run this on /reflect.
| name | commit-msg |
| description | Write a Conventional Commit message from a description of changes. Lead with WHY, not WHAT. |
When the user asks for a commit message, write a Conventional Commit.
<type>(<scope>): <subject>
<body — only if needed>
<type> is one of: feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert.
add, fix, rename — not added, fixes, renaming).Add a body only if the subject can't carry the whole story. The body explains:
git diff is for)Wrap body lines at 72 chars. One blank line between subject and body.
update code — say what and whyfix bug — say which bugWIP — squash before committingrefactor: cleanup — describe the cleanupAsk zero questions. Make a confident first attempt and offer to revise. Most users would rather edit your guess than answer your interview.