frontend-code-review

To review staged frontend changes before a commit, apply a structured quality checklist to your pending working-tree changes. This process catches className, performance, and logic issues by producing prioritized findings with file paths and suggested fixes.

Checklist-driven frontend code review for TypeScript files evaluates targeted .ts and .tsx changes against consistent quality rules. It enforces naming conventions, memoization, and state-management to catch logic issues before merging.

Yes, you can use a checklist to catch Tauri API error handling issues in React. The review process specifically targets Tauri error handling and event cleanup alongside standard frontend quality checks for .tsx files.

Yes, the code review checklist enforces className ordering and naming conventions. It consistently applies these rules to your frontend changes, generating prioritized findings with clear line references and suggested fixes.

The best way to find performance and state-management issues in .tsx files is running a targeted checklist review. It analyzes your code for memoization gaps and state issues, outputting urgent findings with suggested fixes.