code-review

Reviews React 19, Tailwind CSS 4, and Supabase code changes and generates classified issue reports.

16|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill code-review-aibiz-automatyzacje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/AIBiz-Automatyzacje/workspace-template-mobile/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill code-review-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing pull requests and phase implementations by hand is inconsistent and easy to miss critical issues like missing Supabase RLS policies, swallowed errors without Sentry reporting, or race conditions in async React code. This Skill provides a structured, repeatable review workflow with stack-specific checklists and a standardized severity-classified report. ## Core Features & Use Cases - Stack-specific checklists: Loads targeted review criteria for React 19, TypeScript, Tailwind CSS 4, shadcn/ui, Supabase, Sentry, React Query, and React Hook Form based on which files changed. - Severity classification: Categorizes every finding as blocking, important, nit, or suggestion, with a standardized Markdown report including statistics, positives, and a merge recommendation. - Common issue catalog: Ships a reference of frequent mistakes (missing RLS, useEffect data fetching, service_role key leaks, N+1 queries) with wrong/right code examples. - Use Case: After finishing an implementation phase, run the review against the changed files to produce a review-faza-X.md report listing a blocking issue like a table without RLS, plus nits like obsolete forwardRef usage, before merging. ## Quick Start Ask the assistant to review the changed files of the current phase or pull request using the code-review skill and generate the classified report.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request for React 19 and Supabase code?▼

Collect the changed files with git diff, load the matching checklists for each file type, then analyze correctness, security, performance, and race conditions. Classify each finding as blocking, important, nit, or suggestion and generate the standardized Markdown report.

What are common Supabase mistakes found in code review?▼

Frequent issues include tables without Row Level Security policies, using the service_role key in client code, ignoring the error field from query responses, and select("*") leaking sensitive columns. Each has a documented fix with example policies and typed queries.

Does this review approach support React 19 specific patterns?▼

Yes, the checklists cover React 19 changes such as ref as a normal prop instead of forwardRef, direct Context usage instead of Context.Provider, and avoiding manual useMemo or useCallback when the React Compiler is enabled.

When should a code review issue block a merge?▼

Block merges for security vulnerabilities, crashes or data loss, missing RLS policies on user-data tables, and missing Sentry captureException in catch blocks. Performance problems and accessibility gaps are marked important, while naming and style issues are non-blocking nits.

How should feedback be written in a code review?▼

Use concrete file and line references, propose solutions rather than only criticizing, and prefer questions over commands for debatable points. The review-patterns reference provides templates for each severity label plus guidance for disagreements and tight deadlines.