React Code Review That Understands Hooks and Rendering

Most React defects are not syntax errors. They are an effect that runs too often, a dependency array that lies, state derived in the wrong place, or user-controlled markup rendered straight into the DOM. CodeSightAI reviews React changes with one model and has a second model check the result before you read it.

What gets checked in React code

  • Effect dependency arrays that omit values the effect reads, and the stale closures that follow.
  • Effects used for work that belongs in an event handler or in render.
  • State that should be derived instead of stored, and the sync bugs it causes.
  • Missing cleanup on subscriptions, timers and aborted requests.
  • Keys derived from array indexes where the list reorders.
  • dangerouslySetInnerHTML fed from user-controlled data.

Data fetching and state

Fetching in components is where the interesting mistakes live: requests fired on every render, race conditions when a user types faster than the network answers, error states that silently swallow failures, and loading states that never resolve. The review flags these as behaviour problems with a concrete fix, not as style preferences.

React on Supabase

  • Supabase queries in the client that depend on row-level security which is not actually enabled.
  • Service-role keys or other secrets reaching browser code.
  • Realtime subscriptions created per render and never removed.
  • Auth state read before the session has resolved, showing the wrong UI for a moment.

Fixes you can commit

Each finding comes with a before/after suggestion against the real file. On a GitHub pull request you can commit the fix to the branch from the dashboard, after the file contents are verified so the patch never lands in the wrong place.

Frequently asked questions

Does it handle TypeScript React?

Yes. TSX files are reviewed the same way, and type-level problems are reported alongside behavioural ones.

Will it complain about my formatting?

Stylistic nitpicks can be switched off, so the review stays on defects rather than preferences.

Does it work with Next.js or Vite apps?

The review works on the files in your repository, so the build tool does not matter. GitHub is the supported platform today.

Can I try it without connecting a repository?

Yes. Paste a component into the free analyzer and read the review without an account.

Start free

Free plan available. No credit card required.