code_review

Reviews pull requests and detects code smells using structured checklists and linting commands.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill code-review-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code_review
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/code_review
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill code-review-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests consistently is hard: reviewers miss security risks, performance issues, and code smells, and feedback is often vague or inconsistent. This Skill provides a structured, checklist-driven review process covering functionality, quality, security, and performance. ## Core Features & Use Cases - Structured Review Checklists: Covers functionality, code quality (DRY, naming, magic numbers), security (SQL injection, XSS, auth), and performance (N+1 queries, memory leaks). - Code Smell Detection: A reference table of common smells (Long Method, God Class, Deep Nesting) with refactoring solutions, plus detection commands like ESLint complexity rules and SonarQube. - PR Best Practices: Guidance on ideal PR size, description templates, conventional commit messages, and comment prefixes (blocking, suggestion, question, nitpick, praise). - Use Case: When a teammate opens a 350-line PR, run the three-phase workflow (Triage, Deep Dive, Feedback) to verify CI status, check architecture conformance, and leave constructive prefixed comments. ## Quick Start Review this pull request using the code review checklist and flag any code smells, security risks, or missing tests.

Frequently Asked Questions about code_review

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

FAQPage Schema
How do I review a pull request effectively?

Follow a three-phase workflow: Triage (check CI status, PR size, and description clarity), Deep Dive (verify logic, architecture conformance, and test coverage), and Feedback (leave constructive comments and decide to approve or request changes).

How to detect code smells in a codebase?

Use a smell reference table covering Long Method, Large Class, Duplicate Code, and Deep Nesting, then run detection commands like ESLint with a complexity rule, SonarQube scanning, and test coverage reports to quantify issues.

What is the ideal pull request size for review?

Keep PRs under 200 lines for ideal reviewability. PRs between 200-400 lines are acceptable, but anything over 400 lines should be split into smaller changes to maintain review quality.

What security checks should a code review include?

Verify there is no SQL injection or XSS risk, confirm sensitive data is not exposed, and check that authentication and authorization logic is correct. These checks are part of the standard security checklist.

When should I use quality-validator or peer-review instead of code review?

Use code review for PR review, code smell detection, and best practice control. Route deliverable control tasks to quality-validator and document review tasks to peer-review, as those skills cover different scopes.