code-review

Review code changes for spec compliance, quality, security, and performance.

Updated May 2, 2026
One-click install
npx skills add https://github.com/iliaal/compound-engineering-plugin --skill code-review-iliaal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/iliaal/compound-engineering-plugin/tree/main/distillery/generated-skills/code-review
Command: npx skills add https://github.com/iliaal/compound-engineering-plugin --skill code-review-iliaal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, ensuring both adherence to specifications and high standards of code quality, thereby reducing bugs and improving maintainability.

Core Features & Use Cases

  • Two-Stage Review: Conducts sequential reviews for spec compliance first, then code quality.
  • Severity-Ranked Findings: Categorizes issues into Critical, Important, and Minor for prioritized action.
  • Use Case: When a pull request is submitted, use this Skill to perform a thorough review, identifying potential bugs, security risks, and areas for improvement before merging.

Quick Start

Use the code-review skill to review the attached code changes for spec compliance and quality.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a pull request for spec compliance and code quality?

To review a pull request, you can use a two-stage code review process that first verifies spec compliance and then assesses code quality, security, and performance to identify issues with severity rankings.

What is the best way to categorize issues found during a code audit?

During a code audit, issues are best categorized by severity rankings into Critical, Important, and Minor, which helps prioritize actionable feedback for potential bugs and security risks.

Can I use automated code review for auditing code diffs before merging?

Yes, automated code review is applicable for auditing code diffs and pull requests before merging, ensuring high standards of code quality and adherence to specifications to improve maintainability.

Does a two-stage code review check for security vulnerabilities and performance issues?

A two-stage code review does check for security vulnerabilities and performance issues, assessing code quality in its second stage after verifying spec compliance to reduce bugs and improve overall maintainability.

When do I need a security audit during the code review process?

You need a security audit during the code review process when assessing code changes, as the review identifies security risks and provides severity-ranked actionable feedback to ensure standards before merging.