القائمة
Stage the intended changes only, derive a scoped conventional-commit message, branch first if on main, run the staged lint check, and commit. Use when the user asks to commit work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run the full pre-push gate (lint, typecheck, test, build) and triage any failures by stage. Use before pushing or when asked to verify the repo is green.
Scaffold a new client feature folder following the Page→hook→sections pattern, using features/tools as the template. Use when starting a new client feature.
Review a pull request against member-manager's invariants and post inline comments. Use when asked to review a PR.
Reset and seed the local Supabase stack, then run the Playwright E2E suite (or a single spec) and summarize failures. Use when asked to verify end-to-end behavior.
Use when changing UI, styling, theming, logos, imagery, or visual copy in this repo so the result follows the TUM.ai corporate identity. Apply the vendored brand guide, color system, typography, button treatment, and dark/light mode rules before shipping frontend work.
| name | commit |
| description | Stage the intended changes only, derive a scoped conventional-commit message, branch first if on main, run the staged lint check, and commit. Use when the user asks to commit work. |
Commit the current work cleanly.
git status and git diff (and git diff --staged). Identify only the changes
that belong to this unit of work. Do not blindly git add -A unrelated files.main — git branch --show-current. If it's main, create a topic branch first
(git switch -c <type>/<short-slug>); never commit straight to main.git add <paths>).pnpm lint:staged. Fix anything it flags before committing.type(scope): summary where type ∈
feat|fix|refactor|test|ci|docs|style|chore|perf|build. Keep the subject imperative and concise.