code-review

Guide structured code review feedback and verification in subagent-driven development.

2|1|Updated Oct 11, 2025

Search Tags:#code quality #developer tools #code review #best practices #feedback #collaboration #software development

Ready to run

npx skills add https://github.com/rafaelcalleja/claude-market-place --skill code-review-rafaelcalleja

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/rafaelcalleja/claude-market-place/tree/main/plugins/claudekit-skills/skills/code-review
Command: npx skills add https://github.com/rafaelcalleja/claude-market-place --skill code-review-rafaelcalleja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solves?

Ineffective code reviews can lead to missed bugs, inconsistent code quality, and team friction. This skill provides expert guidance for both conducting and receiving code reviews, fostering a culture of quality.

Core Features & Use Cases

Structured Review Process: Guides through a systematic approach to evaluating code for correctness, readability, and maintainability.
Constructive Feedback: Provides best practices for giving and receiving feedback that fosters growth, not defensiveness.
Pre-Submission Verification: Encourages developers to verify their code thoroughly before requesting a review, reducing rework.
Team Collaboration: Promotes a collaborative environment for improving code quality across the team.
Use Case: Conduct a code review for a pull request, focusing on identifying potential security vulnerabilities, ensuring adherence to coding standards, and providing clear, actionable feedback.

Quick Start

Use the code-review skill to guide me through reviewing a pull request for a new feature.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I conduct an effective code review for a pull request?▼

Code reviews systematically evaluate code for correctness, readability, and maintainability. Start by verifying the code meets coding standards, then check for security vulnerabilities and logical errors. Provide clear, actionable feedback that guides improvement rather than creates defensiveness, focusing on the code's quality and alignment with team practices.

What's the best way to give constructive code review feedback?▼

Constructive feedback balances identifying issues with fostering growth. Be specific about what needs improvement, explain the reasoning, and suggest alternatives. Frame comments as collaborative guidance rather than criticism. This approach reduces team friction and encourages developers to learn from reviews instead of becoming defensive.

How should I prepare my code before requesting a review?▼

Pre-submission verification reduces rework and review cycles. Test your code thoroughly, ensure it follows coding standards, check for security issues, and verify it solves the intended problem. Self-review catches obvious mistakes and demonstrates professionalism, making the actual review more focused on substantive feedback.

Can code reviews help catch security vulnerabilities?▼

Yes. Security-focused code reviews identify potential vulnerabilities by examining how data flows, validating input handling, checking authentication and authorization logic, and reviewing dependencies. Systematic review catches issues that automated tools might miss, reducing security risks before code reaches production.

What are common code review mistakes to avoid?▼

Avoid vague feedback, focusing only on style over substance, rushing reviews, or delivering feedback harshly. Don't skip verification that code actually works. Effective reviews balance catching real issues with maintaining team morale and psychological safety, preventing friction while raising quality standards.

How do code reviews improve team collaboration?▼

Code reviews create structured touchpoints for knowledge sharing and collective ownership. They establish consistent quality standards, surface different perspectives on problem-solving, and build trust through transparent, evidence-based feedback. This shared accountability strengthens team cohesion and distributed code understanding.