code-review

Guide engineers through structured code reviews with risk-based modes and checklists.

346|50|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/liza-mas/liza --skill code-review-liza-mas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/liza-mas/liza/tree/main/skills/code-review
Command: npx skills add https://github.com/liza-mas/liza --skill code-review-liza-mas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code Review Protocol provides a disciplined, expectation-driven framework to detect defects, enforce quality, and improve collaboration during code reviews.

Core Features & Use Cases

  • Review Modes: Sanity, Standard, Deep with a decision tree to match risk level.
  • Review Hierarchy & Checklist: Security, Correctness, Data integrity, Architecture & Operability, Performance, Maintainability, and Style.
  • Feedback & Approval: Structured feedback format, escalation paths, and clear acceptance criteria for PRs.

Quick Start

Start a PR review in Standard mode, outline the context and scope, identify blockers, and provide prioritized, actionable feedback using the structured checklist.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I structure a pull request review to catch security and architecture issues?

A structured pull request review uses a formal checklist covering security, correctness, data integrity, architecture, performance, and maintainability to catch defects early and enforce quality.

What is the best way to review large pull requests that impact core architecture?

The best way to review large pull requests is using a Deep review mode, which provides a thorough checklist and decision tree to match the high risk level of core architecture changes.

How do I provide actionable code review feedback with clear approval criteria?

Provide actionable code review feedback by using a structured format that outlines context, identifies blockers, and follows clear acceptance criteria and escalation paths for the PR.

Can I use a standard code review checklist for small diffs and minor changes?

Yes, you can use a Standard review mode for small diffs, which applies the formal review process and checklist proportionate to the lower risk level of minor changes.

When do I need a formal code review process instead of a quick sanity check?

You need a formal code review process instead of a quick sanity check when changes involve data integrity, operability, or security risks that require structured feedback and clear approval criteria.

How does a code review protocol improve collaboration during pull requests?

A code review protocol improves collaboration by enforcing an expectation-driven framework with structured feedback formats and escalation paths, ensuring clear communication and quality enforcement.