code-reviewer

Inspect code diffs for security flaws, bugs, and maintainability issues.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Minhmice/Thuocare --skill code-reviewer-minhmice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/Minhmice/Thuocare/tree/main/.cursor/agents/specialists/code-reviewer
Command: npx skills add https://github.com/Minhmice/Thuocare --skill code-reviewer-minhmice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers and teams verify code changes for correctness, security, and maintainability, preventing bugs and vulnerabilities from progressing into production.

Core Features & Use Cases

  • Risk Assessment: Analyzes code diffs for potential security issues and design flaws.
  • Quality Gate: Acts as an independent review step before code merge or completion.
  • Use Case: A developer submits a pull request; this Skill provides a comprehensive review report highlighting critical and major issues that must be addressed prior to integration.

Quick Start

Ask the code-reviewer to analyze the latest code changes to ensure adherence to best practices and security standards.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I check code changes for security flaws before merging?

To check code changes for security flaws before merging, you analyze the diffs against best practices and security standards. This process inspects code modifications to identify potential vulnerabilities and design flaws, ensuring issues are caught prior to integration.

Can I use automated code review in a continuous integration pipeline?

Yes, automated code review can be used in a continuous integration pipeline. It acts as an independent quality gate that analyzes code changes and test evidence within the local environment, providing prioritized findings before deployment.

What do I need to provide for a code analysis to run successfully?

For a code analysis to run successfully, you must provide access to code diffs, requirements, and test evidence. The analysis tools execute within your local environment to verify correctness and maintainability based on these inputs.

How does code analysis identify maintainability issues in a pull request?

Code analysis identifies maintainability issues in a pull request by inspecting code diffs for design flaws and bugs. It generates a comprehensive review report that highlights critical and major issues requiring attention before integration.

What is the best way to prevent bugs from progressing into production environments?

The best way to prevent bugs from progressing into production is to implement an independent code review step before merge. This verifies code changes for correctness and security, providing prioritized findings that block flawed code from deployment.