القائمة
Create a git commit. Use when ready to commit changes. Creates conventional commit messages focused on why, not what.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | commit |
| description | Create a git commit. Use when ready to commit changes. Creates conventional commit messages focused on why, not what. |
| argument-hint | Optional message hint or --amend flag |
Create a high-quality commit with a message that captures the intent, not just the mechanics.
Run in parallel:
git diff --cached # Staged changes (or git diff if nothing staged)
git status # What's changed
git log --oneline -5 # Match repository style
If the caller provides a reviewed file allowlist or says "staged changes only",
verify git diff --cached --name-only exactly matches that scope and do not run
git add. Stop if unstaged changes make the intended commit ambiguous.
Before writing the message, identify:
The diff shows what changed. The message explains why.
type(scope): concise summary in imperative mood
Optional body explaining WHY this change was made.
Not what changed (the diff shows that), but why.
Before committing, verify:
git add [files] # Stage if needed
git commit -m "..."
Skip git add when the caller requested staged-only behavior.
| Type | Use For |
|---|---|
feat | New feature or functionality |
fix | Bug fix |
refactor | Code restructuring (no behavior change) |
docs | Documentation only |
chore | Maintenance, dependencies, config |
test | Adding or modifying tests |
perf | Performance improvements |
Good: Explains intent
feat(auth): add rate limiting to login endpoint
Prevents brute-force attacks by limiting attempts per IP.
Bad: Just describes the diff
feat(auth): add rate limiter middleware and config
Good: Specific
fix(api): handle null response from payment provider
Bad: Vague
fix(api): fix bug
Add a body when:
Include scope when changes focus on a specific module. Skip when changes span multiple areas or scope is obvious from context.
feat(auth): add OAuth2 provider
fix(api): handle null response
refactor(database): normalize user schema
chore: update dependencies
Analyze unresolved PR review comments and recommend whether to fix, skip, or optionally address each. Use when a PR has review comments and you need a verdict on how to respond.
Open a pull request for the current branch. Use when code is ready for review. Creates concise descriptions focused on the problem being solved.
Karpman Drama Triangle analysis for communication and conflict. Use when reviewing emails, proposals, or scripts for hidden drama dynamics, coaching difficult conversations, analyzing interpersonal conflict, or reframing victim/hero/villain patterns into Creator/Challenger/Coach alternatives.
Audit codebase, assess technical debt, analyze architecture, find structural problems. Use when evaluating code health, planning refactors, or need architectural review. Covers brittleness, coupling, complexity.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Interrogate a plan or design relentlessly — walk each branch of the decision tree and resolve every open decision until nothing vague remains. Use to stress-test a plan, surface edge cases and gaps you missed, get grilled on a design, or when you mention "grill me".