reviewer

Review code changes through multiple specialized roles and risk escalation.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/rubykachu/skill-scaffold --skill reviewer-rubykachu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/rubykachu/skill-scaffold/tree/main/.cursor/skills/reviewer
Command: npx skills add https://github.com/rubykachu/skill-scaffold --skill reviewer-rubykachu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the limitations of single-perspective code reviews by systematically evaluating changes through multiple, specialized roles, ensuring comprehensive coverage and adherence to project standards.

Core Features & Use Cases

  • Multi-Agent Review: Employs distinct perspectives (Content Expert, Skeptic, Constraint Guardian, Integration Reviewer) to identify a wider range of issues.
  • Risk-Based Escalation: Automatically escalates high-risk changes for a more thorough review by @multi-agent-brainstorming.
  • Use Case: After a developer implements a new feature, they can use this Skill to get a review that checks not only for functional correctness but also for adherence to coding conventions, potential security risks, and integration compatibility.

Quick Start

Use the reviewer skill to check the code changes in the current branch.

Frequently Asked Questions about reviewer

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

FAQPage Schema
How does multi-perspective code review improve risk assessment for new features?

Multi-perspective code review improves risk assessment by sequentially applying specialized roles like Content Expert and Skeptic to analyze changes against project conventions. This mechanism systematically identifies issues across scripts and documentation, escalating high-risk changes for deeper analysis.

How do I check code changes against project conventions and security standards?

To check code changes against project conventions and security standards, run a multi-perspective review on your current branch. The process sequentially applies specialized roles to validate YAML frontmatter, enforce file patterns, and identify security issues across orchestration and templates.

What is the best way to automate code review for orchestration scripts and templates?

The best way to automate code review for orchestration scripts and templates is using a multi-agent approach. This method evaluates changes through distinct specialized roles like Constraint Guardian and Integration Reviewer, ensuring comprehensive coverage of functional correctness, security risks, and integration compatibility.

Does multi-agent code review enforce specific file patterns and YAML frontmatter validation?

Yes, multi-agent code review enforces specific file patterns and YAML frontmatter validation. It requires strict adherence to these structural conventions as part of its comprehensive multi-perspective analysis against project standards and risk factors.

When should I escalate high-risk changes during a multi-perspective code review?

You should escalate high-risk changes during a multi-perspective code review when specialized roles identify critical issues in security, orchestration, or integration compatibility. The process automatically escalates these high-risk changes for a more thorough multi-agent brainstorming review.