code-review

Review code against a six-dimension checklist for correctness, security, and maintainability.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/xiaoshuangLi/aibo --skill code-review-xiaoshuangli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/xiaoshuangLi/aibo/tree/main/skills/code-review
Command: npx skills add https://github.com/xiaoshuangLi/aibo --skill code-review-xiaoshuangli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic code review methodology for evaluating code quality, correctness, security, and maintainability. Use this skill when reviewing pull requests, auditing existing code, or preparing code for review.

Core Features & Use Cases

  • Correctness-focused evaluation across code changes and edge cases.
  • Security and vulnerability spotting during reviews, including input validation and dependency checks.
  • Maintainability and readability improvements through naming, structure, and documentation enhancements.
  • Performance considerations and potential optimization opportunities identified during reviews.
  • Use Case: Review pull requests to ensure quality before merge, audit legacy code, and mentor junior developers through constructive feedback.

Quick Start

Ask me to run a code-review on a given PR and follow the standard checklist to produce actionable feedback.

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 on a pull request?

Perform a structured code review by applying a six-dimension checklist covering correctness, security, performance, maintainability, tests, and documentation to catch bugs and ensure quality before merging.

What is the best way to audit legacy code for security and maintainability gaps?

Auditing legacy code for maintainability and security involves systematically evaluating code changes, spotting input validation vulnerabilities, checking dependencies, and suggesting structural improvements.

How do I write constructive code review feedback to mentor junior developers?

Write constructive code review feedback by adopting a mentoring communication style that suggests naming, structure, and documentation enhancements while evaluating correctness and edge cases.

Does static analysis cover performance considerations during a code review?

Static analysis during a code review covers performance considerations by identifying potential optimization opportunities alongside evaluating correctness, security vulnerabilities, and input validation checks.

What should be on a code review checklist for maintainability?

A code review checklist for maintainability should include evaluating naming conventions, structural improvements, readability, documentation completeness, and potential performance optimizations.