code-review

Automates structured, multi-dimensional code review for pull requests.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/RaoXuntian/azurevm-openclaw-backup --skill code-review-raoxuntian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/RaoXuntian/azurevm-openclaw-backup/tree/main/workspace-coding/skills/code-review
Command: npx skills add https://github.com/RaoXuntian/azurevm-openclaw-backup --skill code-review-raoxuntian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic, structured guidance for evaluating code during pull requests to improve security, performance, correctness, and maintainability.

Core Features & Use Cases

  • Review dimensions prioritized as Security → Performance → Correctness → Maintainability → Testing → Accessibility → Documentation
  • Security checklist including SQL injection, XSS, CSRF, authentication, and secrets management
  • Performance checklist addressing N+1 queries, memory usage, and bundle size
  • Correctness checklist for edge cases, null handling, race conditions, and timezone handling
  • Maintainability checklist focusing on naming, SRP, DRY, dead code, and dependency direction
  • Testing checklist covering coverage, edge cases, flaky tests, and mocking discipline
  • Three-pass review process: high-level, line-by-line, then edge cases
  • Severity levels (Critical, Major, Minor, Nitpick) with merge-blocking guidance
  • Guidance on giving actionable, structured feedback with examples

Quick Start

Run the code-review tool on the target pull request to generate a structured, multi-dimension review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I standardize pull request reviews for security and maintainability?

Standardize pull request reviews by applying a structured three-pass process with severity levels and comprehensive checklists across security, performance, correctness, and maintainability to ensure consistent, repeatable code assessments.

What is the best way to check a pull request for security vulnerabilities like SQL injection and XSS?

Check pull requests for vulnerabilities using a dedicated security checklist that evaluates SQL injection, XSS, CSRF, authentication, and secrets management, prioritizing these checks first in the multi-dimension review process.

How do I structure code review feedback to be actionable and consistent?

Structure code review feedback using defined severity levels—Critical, Major, Minor, and Nitpick—along with merge-blocking guidance to provide actionable, repeatable assessments with clear examples for developers.

Does this code review process cover performance and testing edge cases?

Yes, the code review process covers performance by checking N+1 queries and memory usage, and evaluates testing by assessing coverage, edge cases, flaky tests, and mocking discipline through a dedicated line-by-line and edge case review pass.

What checklists are included for maintainability and correctness in code reviews?

Maintainability checklists evaluate naming, SRP, DRY, dead code, and dependency direction, while correctness checklists assess edge cases, null handling, race conditions, and timezone handling during the review.