Menu
Review a pull request against member-manager's invariants and post inline comments. Use when asked to review a PR.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
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.
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 | pr-review |
| description | Review a pull request against member-manager's invariants and post inline comments. Use when asked to review a PR. |
Review a PR (current branch's PR, or one passed as an argument).
gh pr view for context + gh pr diff for the change. Note the PR number.code-reviewer agent with the diff and the repo checklist:
sensitiveData.ts; authZ on every route;
no secrets; no public DB crypto functions.@/ across features; file-size limits.shared/ framework-free; DB parity.pnpm lint/typecheck/relevant tests, not by trusting the diff.gh (review comments on the diff lines), severity-tagged
[BLOCKER|MAJOR|MINOR|NIT]. Summarize the verdict in a top-level comment.