code-review

Orchestrates subagents to review pull requests using code-review skills.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill code-review-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/code-review
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill code-review-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a pull request thoroughly requires checking many dimensions at once, and a single-pass review often misses issues. This Skill coordinates multiple specialized code-review skills as parallel subagents and consolidates every finding into one numbered report. ## Core Features & Use Cases - Multi-subagent orchestration: Spawns one subagent per code-review-* skill, passing the full skill path and using high reasoning effort. - Complete findings report: Returns every issue from every subagent as numbered Markdown findings, each with a specific file path and line number. - GitHub integration: Adds a code-reviewed label when the reviewer is the pull request owner, and never posts GitHub comments unless explicitly asked. - Use Case: Before merging a large pull request, run this Skill to fan out specialized reviewers and receive a single consolidated, numbered list of all detected issues. ## Quick Start Run a final code review on this pull request using all code-review skills and report every finding with file paths and line numbers.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run a final code review on a pull request with subagents?▼

Invoke the code-review skill, which spawns one subagent per code-review-* skill with the full skill path and high reasoning effort. It aggregates every subagent's findings into a single numbered Markdown report with file paths and line numbers.

How are code review findings reported?▼

Findings are returned as raw Markdown, numbered for easy reference. Each finding must include a specific file path and line number, and every issue from every subagent is included with no cap on the number of findings.

Does the code review skill post comments on GitHub?▼

No, it does not leave GitHub comments unless explicitly asked. The only automatic GitHub action is adding a code-reviewed label when the user running the review owns the pull request.

When is the code-reviewed label added to a pull request?▼

The label is added only when the GitHub user running the review is the owner of the pull request. Reviews run by non-owners produce findings without labeling the pull request.

What are the limitations of subagent-based code review?▼

The orchestrator depends on the availability and coverage of the individual code-review-* skills, so gaps in those skills mean gaps in the review. It also requires subagent support and high reasoning effort, which increases compute cost per review.