code-review

Automate evidence-based code reviews with scout-based edge-case detection.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mchien15/wrenai --skill code-review-mchien15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/mchien15/wrenai/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/mchien15/wrenai --skill code-review-mchien15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews are often inconsistent and slow, leading to defects and wasted time. This Skill provides a rigorous, evidence-based review process to improve quality, prevent regressions, and ensure verifiable completion claims.

Core Features & Use Cases

  • Scout-based edge-case detection to surface issues before review
  • Parallel reviewer workflows to speed up multi-file changes
  • Verification gates that enforce evidence-based completion
  • Task-pipeline orchestration to manage the review lifecycle

Quick Start

Invoke the code-review skill after implementing a feature or change to initiate the scout-and-review workflow.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate evidence-based code reviews before merging?

Automated evidence-based code reviews enforce verification gates to catch defects before integration. Scout-based edge-case detection surfaces issues early, while parallel multi-file reviews speed up the process and ensure verifiable completion claims.

What is scout-based edge-case detection in a code review pipeline?

Scout-based edge-case detection is a mechanism that proactively surfaces potential issues before the formal review begins. It operates within a task-pipeline orchestration to identify boundary conditions and prevent regressions prior to integration.

How do I run parallel reviews for multi-file changes?

Parallel reviewer workflows enable multi-file code reviews by processing changes concurrently. This orchestration speeds up the review lifecycle while enforcing traceable baselines and verification gates for evidence-based completion.

When do I need to enforce verification gates in a code review?

Verification gates are needed when you must ensure verifiable completion claims and prevent regressions. They enforce evidence-based checks during the review pipeline, guaranteeing that feature implementation meets traceable baselines before merging.

Does this code review approach work for catching regressions in feature implementations?

Yes, this code review approach prevents regressions by applying rigorous, evidence-based checks after feature implementation. Scout-based detection and traceable baselines ensure any introduced defects are caught before integration.