reviewing-code

Identify and flag code issues with priority-based review workflows.

2|Updated Jan 29, 2026

Search Tags:#performance #security #best-practices #code-review #test-coverage #n-plus-one-queries

Ready to run

npx skills add https://github.com/oryanmoshe/agent-skills --skill reviewing-code-oryanmoshe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/oryanmoshe/agent-skills/tree/main/skills/reviewing-code
Command: npx skills add https://github.com/oryanmoshe/agent-skills --skill reviewing-code-oryanmoshe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code changes for bugs, performance issues, security problems, and best practice violations. Use when reviewing PRs, before committing, after making code changes, or when user asks to review, check, or look over code. Catches N+1 queries, missing error handling, React hooks issues, test coverage gaps, and security vulnerabilities.

Core Features & Use Cases

Automated checklist-driven code review that prioritizes P0/P1/P2 issues.
Detects performance bottlenecks, null-safety gaps, and security vulnerabilities during reviews.
Use Case: When evaluating a PR, the skill surfaces potential N+1 queries, missing tests, and unsafe patterns before merge.

Quick Start

Run the reviewing-code skill during PR reviews to consistently surface and address critical issues early in the development process.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema

How do I detect N+1 queries and security vulnerabilities during a pull request code review?▼

Code review processes can detect N+1 queries and security vulnerabilities by applying a priority-based checklist during PR evaluation. This surfaces performance bottlenecks, null-safety gaps, and unsafe patterns before merge, preventing critical bugs and security problems from reaching production.

What is the best way to prioritize issues found when reviewing code changes?▼

Prioritizing code review issues involves categorizing findings into P0, P1, and P2 severity levels. This priority-based workflow systematically flags critical security vulnerabilities and performance bottlenecks first, ensuring high-impact problems are addressed before minor best-practice violations.

Can I use an automated code review checklist to catch missing test coverage and React hooks issues?▼

Automated code review checklists catch missing test coverage and React hooks issues by systematically scanning code changes. The review process identifies test-coverage shortfalls and framework-specific unsafe patterns, ensuring comprehensive validation before changes are merged.

When do I need to run a code review for error handling gaps and performance bottlenecks?▼

Code reviews for error handling gaps and performance bottlenecks are needed during pull requests, pre-merge checks, post-change reviews, and ad-hoc code inspections. Running reviews at these stages prevents bugs and performance issues early in the development lifecycle.

Does automated code inspection work for ad-hoc code checks outside of standard pull requests?▼

Automated code inspection works for ad-hoc code checks outside standard pull requests by applying the same priority-based review workflow. It consistently identifies security vulnerabilities, N+1 queries, and error handling gaps during post-change reviews or spontaneous code evaluations.

What are the limitations of checklist-driven code reviews for complex security problems?▼

Checklist-driven code reviews are limited to identifying known patterns like N+1 queries, missing tests, and common security vulnerabilities. They may not catch novel, complex security problems or zero-day vulnerabilities that fall outside established best-practice violations and automated detection rules.