react-review
React Review
Code review specializzato per React 18/19 SPA (Vite / CRA). Basato sui 10 pattern più comuni di bug React + trasversali fondamentali. Opera in plan mode: propone, non esegue.
Language rule: detect the language of the user's input and respond entirely in that language — including section headers, explanations, and questions. Never switch languages mid-conversation.
Step 0: Scope selection
Se l'invocazione contiene già un path di file → salta il menu, usa solo quel file (Scope 1).
Altrimenti mostra il menu e aspetta la risposta:
| Input utente | Scope rilevato | Da chiedere ancora |
|---|---|---|
file <path> / controlla questo file <path> |
Scope 1 – File specifico | path se non incluso |
branch / branch diff / review branch |
Scope 2 – Branch diff | base branch — chiedi sempre esplicitamente, non inferire da git remote (hotfix/release safety) |
commit <hash> |
Scope 3 – Commit specifico | niente |
commit (senza hash) |
Scope 3 – Commit specifico | "Quale commit? (hash o 'last')" |
modifiche / uncommitted / controlla modifiche |
Scope 4 – Uncommitted | niente |
More from marcoax/skills
code-review
>
10pessimistic-code-review
>
10grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
8skill-optimizer
>
8current-file-review
Review changes in one explicitly identified current or open file against project best practices. Use only when the user clearly refers to the current file, says "this file", "current file", "open file", or provides a single file path to review. Do not use for generic review requests, branch diffs, commits, or repository-wide review; use code-review or a stack-specific review skill instead. Operates in PLAN MODE - proposes improvements, waits for approval before executing.
8task-spec-creator
Generate a structured TASK_SPEC.md for a single implementation task, sprint ticket, or technical work item by interviewing the developer. Use when the user wants to define one concrete task, capture implementation requirements, document acceptance criteria, or says things like "creiamo una specifica", "voglio definire la task", "ho un ticket da implementare", or "partiamo dalla specifica". Do not use for product-level feature discovery or PRDs; use write-a-prd for that. Do not use for incremental refactor roadmaps; use request-refactor-plan for that.
7