review_code

Review Hono and React monorepo code against project conventions and best practices.

Updated Feb 8, 2026

Search Tags:#typescript #code review #best practices #react #monorepo #hono #convention

Ready to run

npx skills add https://github.com/raulnq/node-hono-react-monorepo --skill review-code-raulnq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review_code
Source: https://github.com/raulnq/node-hono-react-monorepo/tree/main/.claude/skills/review-code
Command: npx skills add https://github.com/raulnq/node-hono-react-monorepo --skill review-code-raulnq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code for adherence to project conventions, common mistakes, and best practices, ensuring a higher quality and more maintainable codebase.

Core Features & Use Cases

Convention Enforcement: Checks imports, TypeScript usage, backend endpoint patterns, Drizzle schema definitions, and frontend component structures against established project guidelines.
Error Detection: Identifies potential bugs, security vulnerabilities, and performance issues.
Use Case: Before merging a pull request, use this Skill to perform a thorough automated review, catching potential issues early and reducing the burden on human reviewers.

Quick Start

Use the review_code skill to check the staged changes in the current branch.

Frequently Asked Questions about review_code

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

FAQPage Schema

How do I automate code reviews for a Hono and React monorepo?▼

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.

What are the best practices for checking TypeScript imports and Drizzle ORM schema definitions?▼

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.

Can I use an automated PR check to enforce frontend component structures in a React monorepo?▼

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.

How does an automated convention adherence check identify common mistakes in backend endpoints?▼

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.

Do I need to stage my Git changes before running an automated code review?▼

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.