code-reviewer

Reviews code diffs for bugs, security vulnerabilities, and performance issues, producing prioritized review reports.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/marketiv-id/marketiv-web --skill code-reviewer-marketiv-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/marketiv-id/marketiv-web/tree/main/00_BACKEND/.agents/skills/code-reviewer
Command: npx skills add https://github.com/marketiv-id/marketiv-web --skill code-reviewer-marketiv-id

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing pull requests thoroughly is time-consuming and inconsistent—critical issues like SQL injection, N+1 queries, and missing edge-case handling often slip through when reviewers lack a systematic process. ## Core Features & Use Cases - Structured Review Workflow: Follows a five-step process (context, structure, details, tests, feedback) with checkpoints to ensure nothing is missed. - Security & Performance Detection: Identifies OWASP Top 10 vulnerabilities, N+1 queries, magic numbers, deep nesting, and missing error handling with concrete before/after code examples. - Prioritized Report Generation: Produces a categorized report (critical, major, minor, praise, questions) with a clear verdict of Approve, Request Changes, or Comment. - Use Case: When a teammate opens a pull request, invoke this Skill to audit the diff for injection risks and query performance, then receive a ready-to-post review report with actionable feedback. ## Quick Start Review the current pull request diff for security vulnerabilities, performance issues, and test coverage, then produce a prioritized review report.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a pull request for security vulnerabilities?▼

Review pull requests by checking for OWASP Top 10 issues: SQL injection from string-interpolated queries, missing input validation, hardcoded secrets, and broken authentication. Use parameterized queries and validate all user input as baseline fixes.

How to detect N+1 query problems in code reviews?▼

Detect N+1 queries by looking for database calls inside loops, such as fetching a related record per iteration. Fix them with eager loading (e.g., include or prefetch_related) or batch loading all required IDs in a single query.

What should a code review report include?▼

A code review report should include a summary, critical issues that block merge, major issues like performance or design problems, minor suggestions, positive feedback, questions for the author, and a verdict of Approve, Request Changes, or Comment.

Should code review check spec compliance before code quality?▼

Yes, verify spec compliance before reviewing code quality. Confirming the implementation matches requirements first prevents wasting effort polishing code that builds the wrong feature or misses requested functionality.

When should a reviewer request changes instead of approving?▼

Request changes when critical issues exist, such as security vulnerabilities, data loss risks, or crashes, or when major issues like N+1 queries and missing edge-case handling significantly affect performance or maintainability.