القائمة
Generate git commit messages, splitting work into granular commits by concern. Use when user says "commit this", "write a commit", "commit message", or invokes /commit.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Write PostgreSQL trigger functions and migrations for this Supabase project. Enforces all security and performance rules derived from the project's migration history to avoid Supabase advisor warnings (lints 0011, 0028, 0029).
Perform thorough, structured code review on a PR. Detects stack/conventions from the codebase, checks linked issues for acceptance criteria, then reviews the diff with severity-graded findings.
Methodically work through PR review comments one-by-one. Fetches comments via gh CLI, explains each reviewer comment, assesses its validity, proposes a solution, waits for user approval, implements, then moves to the next comment.
Zod 4 syntax reference and migration guide. Use when writing Zod schemas to ensure correct Zod 4 patterns are used instead of deprecated Zod 3 syntax.
This skill should be used when the user asks "how does this work", "what patterns are used here", "show me how this is done in the codebase", or before implementing features to understand existing conventions. Explores codebase patterns for types, components, validation, data fetching, and file organization without making any changes.
This skill should be used when the user reports a bug, asks to "fix this bug", "debug this issue", "something is broken", "this isn't working", or requests investigation of unexpected behavior. Enforces minimal scope changes, prevents touching working code, and includes build verification steps.
| name | commit |
| description | Generate git commit messages, splitting work into granular commits by concern. Use when user says "commit this", "write a commit", "commit message", or invokes /commit. |
Single-line commit message. No body, no exceptions.
Split staged/pending changes into multiple commits by concern — never one giant commit for a full feature.
<type>(<scope>): <imperative summary>
feat, fix, refactor, perf, docs, test, chore, build, ci, styleprojects, ui, hooks) — required unless truly globalfeat(projects): add archive toggle to list viewfix(auth): correct token expiry comparisonrefactor(ui): extract shared button variantschore(hooks): update pre-commit lint config