code-reviewer

Review code for correctness, quality, and security vulnerabilities.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/baphled/dotopencode --skill code-reviewer-baphled
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/baphled/dotopencode/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/baphled/dotopencode --skill code-reviewer-baphled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring that code is not only functional but also adheres to high standards of quality, security, and architectural integrity.

Core Features & Use Cases

  • Comprehensive Review: Guides reviews across correctness, quality, and safety.
  • Checklists & Guidance: Provides actionable checklists and identifies common code smells and anti-patterns.
  • Use Case: Before merging a pull request, use this Skill to systematically check for bugs, security vulnerabilities, and adherence to best practices, ensuring a robust codebase.

Quick Start

Use the code-reviewer skill to perform a thorough review of the latest changes in the current branch.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I conduct a code review for a pull request?

To conduct a pull request code review, systematically check code correctness, quality, and security vulnerabilities using actionable checklists. This process validates changes against best practices and architectural integrity before merging.

What should I look for when reviewing code for security vulnerabilities?

When reviewing code for security vulnerabilities, identify common anti-patterns and code smells that expose risks. The review process applies core principles of security and correctness to ensure a robust, protected codebase.

Can I use automated code review to check architectural integrity?

Yes, automated code review can check architectural integrity by validating changes against established architectural principles. This ensures structural correctness and adherence to design guidelines during the review process.

What is the best way to perform a self-review before merging code?

The best way to perform a self-review before merging is to evaluate your own code for correctness, quality, and safety. Following a structured checklist identifies bugs and security issues early, ensuring robust code.

Does this code review process provide constructive feedback for refactoring?

Yes, this code review process emphasizes constructive feedback to guide refactoring efforts. It identifies code smells and anti-patterns while ensuring reviews focus on intent and architectural improvements.

Why does code review need to focus on correctness and intent?

Code review needs to focus on correctness and intent to ensure the implementation accurately solves the targeted problem. Validating these core principles prevents functional bugs and maintains architectural integrity.