review_code

Automating code reviews for a Hono and React monorepo involves analyzing TypeScript imports, backend endpoints, Drizzle ORM schemas, and frontend components against established project conventions. This automated checklist identifies potential bugs and convention violations before merging a pull request.

Best practices for checking TypeScript imports and Drizzle ORM schema definitions include validating import structures, verifying ORM usage patterns, and enforcing project conventions. Automated reviews detect common mistakes, security vulnerabilities, and performance issues within these specific technologies.

Yes, you can use an automated PR check to enforce frontend component structures in a React monorepo. The review process analyzes staged changes and evaluates frontend component patterns against detailed project guidelines to ensure consistency and maintainability.

An automated convention adherence check identifies common mistakes in backend endpoints by analyzing the staged code against a detailed checklist. It evaluates endpoint patterns, detects security vulnerabilities, and flags deviations from established Hono backend guidelines.

Yes, you need to stage your Git changes before running an automated code review. The review process specifically targets the staged changes in the current branch to analyze imports, TypeScript usage, and component structures against the project's conventions.