code-review
Code Review
Comprehensive code review with multiple scopes. Operates in plan mode: proposes, does not execute.
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: Interactive Scope Selection
Show the scope menu UNLESS the user's input already specifies a scope. Use the table below to decide:
| User input matches | Detected scope | Still ask for |
|---|---|---|
file <path> / check this file <path> / check file <path> |
Scope 1 – Current file | path (if not in input) |
branch / branch diff / review branch |
Scope 2 – Branch diff | base branch — always ask explicitly: do NOT infer from git remote — user may be on a hotfix/release branch where the default would be wrong |
commit <hash> / review commit <hash> (hash provided) |
Scope 3 – Specific commit | nothing |
commit / review commit (no hash) |
Scope 3 – Specific commit | "Which commit? (provide hash or type 'last')" |
changes / uncommitted / controlla modifiche / modifiche |
Scope 4 – Uncommitted | nothing |
If the input does not match any row above, show this menu and wait for the user to pick:
More from marcoax/skills
pessimistic-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.
7prd-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
7