code-review

Performs structured code reviews with checklists for quality, security, and performance.

5|4|Updated Jan 13, 2026

Search Tags:#git #code-quality #quality-assurance #code-review #pull-request #review-checklist #team-workflow

Ready to run

npx skills add https://github.com/itsnex1s/awesome-claude-skills --skill code-review-itsnex1s

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/itsnex1s/awesome-claude-skills/tree/main/skills/code-review
Command: npx skills add https://github.com/itsnex1s/awesome-claude-skills --skill code-review-itsnex1s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requests and performs code reviews to improve quality, security, and maintainability.

Core Features & Use Cases

Structured review requests: Provide context, scope, and rationale to reviewers.
Comprehensive checklists: Cover functionality, correctness, quality, security, and performance.
Guidance for reviewers and authors: Etiquette, response expectations, escalation paths, and collaboration norms.
Commands & workflows: Use standard review practices and common tooling (e.g., GitHub CLI) to request, view diffs, and merge.
Best practices: Encourage small, frequent reviews, clear PR descriptions, and traceable decisions.

Quick Start

Provide a concise PR description with change summary, attach context, and reference related issues.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I perform a structured code review for a pull request?▼

To perform a structured code review, provide a concise PR description with a change summary, attach context, and reference related issues. This enforces consistent review processes by checking functionality, quality, security, and performance.

What should be included in a code review request to improve quality and maintainability?▼

A code review request should include structured context, scope, and rationale for reviewers. Providing a clear change summary and referencing related issues ensures reviewers have the necessary context to evaluate maintainability effectively.

What checklists should I use when reviewing code for security and performance?▼

Comprehensive code review checklists should cover functionality, correctness, quality, security, and performance. These checklists enforce structured context and consistent review processes to guide both reviewers and authors.

Can I use GitHub CLI to view diffs and request code reviews?▼

Yes, you can use common tooling like the GitHub CLI to request reviews, view diffs, and merge pull requests. This integrates standard review practices directly into your team workflow for clear guidance.

What are the best practices for team workflow when reviewing pull requests?▼

Best practices for pull request reviews encourage small, frequent reviews, clear PR descriptions, and traceable decisions. They also define etiquette, response expectations, and escalation paths for effective collaboration.

When do I need a formal code review process for my team workflow?▼

You need a formal code review process when your team requires structured context, consistent review standards, and clear guidance for both reviewers and authors to ensure software quality, security, and maintainability.