code-review

Analyze code changes across six review areas with remediation steps.

218|14|Updated Apr 5, 2025
One-click install
npx skills add https://github.com/cin12211/orca-q --skill code-review-cin12211
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/cin12211/orca-q/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/cin12211/orca-q --skill code-review-cin12211

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to perform thorough, structured code reviews that surface root causes and systemic patterns, reducing defects and maintenance costs after significant changes.

Core Features & Use Cases

  • Six focused review areas: architecture & design, code quality, security & dependencies, performance & scalability, testing coverage, and documentation & API design.
  • Actionable feedback: provides concrete remediation steps, rationale, and prioritized recommendations.
  • Parallel review capability: supports simultaneous evaluations across multiple modules or pull requests to speed up the review process.
  • Root-cause analysis: identifies underlying design or process issues rather than surface-level defects.
  • Documentation alignment: ensures API docs and design notes reflect implemented changes.
  • Developer onboarding support: guides new contributors with clear criteria for code quality and architecture expectations.

Quick Start

Submit a code change or repository URL to initiate a review. The skill will analyze the diff and generate structured, actionable feedback tailored for developers and teams.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I get actionable code review feedback for pull requests?

Actionable code review feedback for pull requests requires analyzing code changes across six aspects: architecture, code quality, security, performance, testing, and documentation. It delivers root-cause analysis and concrete remediation steps rather than surface-level defect lists.

What is the best way to perform a structured code review across multiple modules?

Structured code review across multiple modules is best performed by evaluating architecture, security, and testing quality in parallel. This approach surfaces systemic design patterns and provides prioritized recommendations with clear rationale for development teams.

Can I review API design and documentation alignment as part of a code review?

Reviewing API design and documentation alignment is a core part of comprehensive code reviews. It ensures API docs and design notes accurately reflect implemented changes by checking documentation quality against the actual code diff.

How do I identify root causes of code quality and security issues during a review?

Identifying root causes of code quality and security issues involves analyzing underlying design flaws rather than just surface defects. It requires structured critique that pinpoints process issues and provides concrete remediation steps for developers.

Does this code review approach support evaluating performance and scalability?

Evaluating performance and scalability is a supported focus area of structured code reviews. It analyzes code changes to deliver deep feedback on potential bottlenecks, ensuring systems scale effectively and meet performance expectations.

What do I need to provide to start an automated code review?

To start an automated code review, you need to submit a code change or repository URL. The system analyzes the diff to generate structured, actionable feedback tailored to developers and teams across six key focus areas.