code-review

Evaluate source changes for correctness, security, performance, and maintainability issues.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/lava-chen/duya --skill code-review-lava-chen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/lava-chen/duya/tree/main/packages/agent/skills/development/code-review
Command: npx skills add https://github.com/lava-chen/duya --skill code-review-lava-chen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers systematically evaluate code changes for correctness, security, performance, and maintainability while providing constructive feedback that improves collaboration.

Core Features & Use Cases

  • Structured Review Process: Guides reviewers through preparation, review dimensions, feedback delivery, and review cycles.
  • Quality Checklists: Covers correctness, security, performance, maintainability, and special cases such as large changes or emergency fixes.
  • Use Case: A developer reviewing a pull request can use this Skill to identify risks, write actionable comments, and provide a consistent approval or change request assessment.

Quick Start

Use the code-review skill to review this pull request for correctness, security issues, performance concerns, and maintainability improvements.

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?

A structured code review evaluates source changes across correctness, security, performance, and maintainability. Reviewers apply severity classification and constructive feedback practices to identify risks and recommend actionable improvements during the engineering workflow.

What should I check during a software quality review?

A software quality review checks correctness, security vulnerabilities, performance bottlenecks, and maintainability issues. Use quality checklists to systematically evaluate code changes and provide consistent approval or change request assessments for collaborative development.

How do I write constructive code review feedback?

Constructive code review feedback requires structured review criteria and severity classification. Reviewers identify risks in source changes and deliver actionable comments that improve collaboration and recommend specific improvements for maintainability and correctness.

Can I use this approach for reviewing emergency fixes and large code changes?

Yes, the code review process covers special cases including large changes and emergency fixes. Structured quality checklists ensure reviewers still evaluate correctness, security, performance, and maintainability issues effectively in time-sensitive collaborative development scenarios.

What is the best way to identify security and maintainability risks in code changes?

The best way to identify security and maintainability risks is applying structured review criteria during code review. Systematically evaluate source changes for correctness, performance, and maintainability issues, using severity classification to prioritize risks and recommend improvements.