code-reviewer

Review code diffs and files for bugs, security, and performance issues.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/luyangliuable/claude-setup --skill code-reviewer-luyangliuable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/luyangliuable/claude-setup/tree/main/.agents/skills/code-reviewer
Command: npx skills add https://github.com/luyangliuable/claude-setup --skill code-reviewer-luyangliuable

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you perform thorough code reviews without missing critical bugs, security vulnerabilities, performance regressions, or maintainability problems. It turns a manual, inconsistent review process into a structured workflow with clear priorities and actionable feedback.

Core Features & Use Cases

  • Bug and risk detection: Identifies logic errors, edge cases, insecure patterns, N+1 queries, and architectural concerns.
  • Structured review reports: Produces prioritized feedback grouped into critical, major, minor, questions, and positive notes.
  • Review guidance and templates: Uses reference materials for checklists, common issues, feedback examples, and report formatting.
  • Use case: Review a pull request for correctness, security, test coverage, and design fit before merge.

Quick Start

Ask the code reviewer skill to analyze this pull request and return a prioritized review report with bugs, security issues, and suggested fixes.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a pull request for security vulnerabilities and bugs?

A code review identifies bugs, security vulnerabilities, and performance issues by analyzing code diffs and files. It transforms a manual process into a structured workflow, producing a prioritized report with critical, major, and minor feedback grouped by severity.

What is the best way to structure code review feedback for a development team?

Structuring code review feedback requires grouping issues into critical, major, minor, questions, and positive notes. This prioritized format provides actionable feedback, examples, and questions for the author, ensuring the development team can address architectural concerns and risks efficiently.

Can I audit existing code quality and spec compliance without an active pull request?

Yes, you can audit code quality and check spec compliance without an active pull request. By analyzing existing files and codebases, the review process identifies naming problems, architectural concerns, and refactoring opportunities to maintain software engineering standards.

Does automated code review catch architectural concerns and N+1 query performance issues?

Automated code review does catch architectural concerns and N+1 query performance issues. It evaluates code diffs to detect performance regressions, insecure patterns, and edge cases, ensuring the codebase maintains structural integrity and optimal query performance.

What should be included in a refactoring assessment to ensure maintainability?

A refactoring assessment should include analysis of architectural concerns, naming problems, and logic errors. It produces a structured review report with prioritized actionable feedback, ensuring the refactored code maintains high quality and addresses maintainability problems.