code-review

Review pull requests using a hierarchical security-to-style checklist.

Updated Aug 23, 2026

Search Tags:#feedback #software-quality #quality-assurance #code-review #pull-request #review-process

Ready to run

npx skills add https://github.com/Abkr1/liza --skill code-review-abkr1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Abkr1/liza/tree/main/skills/code-review
Command: npx skills add https://github.com/Abkr1/liza --skill code-review-abkr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is risk mitigation, not gatekeeping. The goal is catching issues the author couldn't see — and occasionally sharing a better pattern when it genuinely helps.

Core Features & Use Cases

Establishing context before reviewing to ensure alignment with intent and scope.
Providing a structured review path that emphasizes security, correctness, data integrity, architecture, performance, maintainability, and style.
Guidance on selecting review modes and communicating actionable feedback with clear rationale and escalation paths.

Quick Start

Use the code-review skill to guide a review session on a PR: establish context, choose a mode (default Standard), apply the Review Hierarchy to surface blockers, and produce actionable feedback with rationale.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I do a structured code review on a pull request?▼

A structured code review establishes context first, then applies a hierarchical path checking security, correctness, data integrity, architecture, performance, maintainability, and style to produce actionable feedback with clear rationale.

What is the correct hierarchy for a reliable code review process?▼

The code review hierarchy prioritizes security, correctness, data integrity, architecture and operability, performance, maintainability, and style, ensuring risk mitigation and reliability are addressed before stylistic feedback.

How do I provide actionable feedback during a code review?▼

Actionable code review feedback includes clear rationale for each suggestion and a defined escalation path, ensuring the communication focuses on catching issues the author missed rather than gatekeeping.

Can I use this code review process for patches across diverse projects?▼

Yes, the code review approach is applicable to pull requests and patches across diverse projects and teams where reliability and maintainability are priorities, adapting to different scopes and intents.

What modes are available when reviewing a pull request?▼

The code review process offers standard review modes, defaulting to Standard mode, to guide the session and apply the review hierarchy to surface blockers effectively.

Why should I establish context before starting a code review?▼

Establishing context before a code review ensures alignment with the intent and scope of the pull request, allowing the reviewer to focus on relevant risk mitigation rather than missing the author's goals.