القائمة
Stage all relevant changes and commit with an auto-generated conventional commit message. Use when the user asks to commit changes, commit work, make a commit, or save progress.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to evaluate, score, review, or automatically improve an existing agent skill (a SKILL.md) — e.g. "optimize this skill", "score my skill", "review my SKILL.md", "how good is this skill", "auto-optimize", "improve skill quality". Use when a skill needs quality assessment against a rubric or iterative refinement.
Distills a session's repeatable workflow into a new project skill in .claude/skills/. Use when a session solved a non-trivial, repeatable problem and the workflow is worth capturing for reuse — e.g. "save this", "distill this", "turn this into a skill", "capture this workflow", "make a skill from this", or at the end of a session that produced a reusable pattern.
Use when the user wants to capture, replicate, or distill how a specific person (or topic/role) thinks into a reusable thinking-framework skill — e.g. "distill Munger", "make a Feynman skill", "build an X-perspective", "how does <person> think", or updating an existing <person>-perspective skill. Also use when the user expresses a vague need for a thinking partner or decision lens ("help me improve decision quality", "I need a mental-model advisor", "is there a way of thinking that helps me see business clearly").
Refines an existing project skill in .claude/skills/ with new learnings from the current session. Use when updating or improving an existing skill, or when distill-session identifies the learning extends an existing skill rather than warranting a new one — e.g. "update SKILL.md", "improve this skill", "extend this skill", "refine this skill", "tighten the skill description", or "this skill didn't trigger".
Tags the current git repository with a new version tag. Use when marking a release point in git history.
Picks the right Kubernetes Deployment update strategy (RollingUpdate / Recreate / Blue-Green / Canary) for the situation. Use when configuring a new Deployment, changing rollout config, or deciding how to ship a risky change.
| name | commit |
| description | Stage all relevant changes and commit with an auto-generated conventional commit message. Use when the user asks to commit changes, commit work, make a commit, or save progress. |
| argument-hint | [optional context or hint for the commit message] |
| user-invocable | true |
| allowed-tools | Bash, Read |
| context | fork |
| model | haiku |
Stage and commit with a conventional commit message — no confirmation needed.
If an argument was provided, treat it as a hint for the message (ticket number, feature name, etc.).
git status + git diff HEAD — if sensitive files appear (.env, credentials, keys), warn and stop.type(scope): summary — imperative mood, under 72 chars, body only when the why isn't obvious.git add -A then commit.feat · fix · refactor · docs · chore · test · style · perf · ci · build · skill (AI skill/prompt changes)
Nothing to commit? Report status and stop.