code-review

Review code changes for bugs, style, security, and maintainability issues.

1|Updated Jun 14, 2025

Search Tags:#security #best-practices #quality-check #code-review #pull-request #architecture-review

Ready to run

npx skills add https://github.com/kishan04rajput/ai-ide-rules --skill code-review-kishan04rajput

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kishan04rajput/ai-ide-rules/tree/main/global_skills/code-review
Command: npx skills add https://github.com/kishan04rajput/ai-ide-rules --skill code-review-kishan04rajput

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify bugs, style issues, security gaps, and maintainability problems in code changes.

Core Features & Use Cases

Structured Checklist: Applies a comprehensive review checklist covering Correctness & Logic, Quality & Maintainability, Performance & Scalability, and Security.
Actionable Feedback: Flags issues with clear severity levels ([BLOCKER], [WARN], [NIT]) and suggests concrete fixes.
PR & Collaboration Focus: Ideal for pull request reviews, code quality gates, and onboarding new engineers to code standards.

Quick Start

To review a patch, start with the 4-step process: 1) assess intent and architecture, 2) run the correctness and maintainability checks, 3) evaluate performance implications and security considerations, 4) provide constructive, actionable feedback with recommended changes.

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 for security gaps and maintainability issues?▼

To review a pull request for security gaps and maintainability issues, assess the code intent, run correctness checks, evaluate performance and security considerations, and provide actionable feedback labeled as BLOCKER, WARN, or NIT.

What is a structured code review checklist for bugs and style issues?▼

A structured code review checklist evaluates code changes across four categories: Correctness and Logic, Quality and Maintainability, Performance and Scalability, and Security, ensuring comprehensive bug, style, and vulnerability detection.

How do I provide actionable feedback during a code quality gate review?▼

You provide actionable feedback during a code quality gate review by flagging identified issues with clear severity levels—BLOCKER, WARN, or NIT—and suggesting concrete fixes to improve the patch.

Can I use this code review process for onboarding new engineers to code standards?▼

Yes, you can use this code review process for onboarding new engineers to code standards across multiple languages by applying the 4-category review checklist to their pull requests.

What's the best way to identify security gaps in code changes?▼

The best way to identify security gaps in code changes is to evaluate security considerations as part of a 4-step review process that assesses intent, correctness, performance, and maintainability.

When do I need a 4-category architecture review for my code changes?▼

You need a 4-category architecture review for your code changes during pull request reviews and quality gates to systematically identify bugs, style issues, security gaps, and maintainability problems.