review

Coordinate acceptance criteria verification and multi-perspective reviews on GitHub pull requests.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/saitoco/wholework --skill review-saitoco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/saitoco/wholework/tree/main/skills/review
Command: npx skills add https://github.com/saitoco/wholework --skill review-saitoco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically coordinates and runs acceptance criteria verification, multi-perspective reviews, and summary posting for pull requests, reducing manual toil and speeding up quality checks.

Core Features & Use Cases

  • Automated acceptance-criteria verification and multi-perspective code review
  • Issue resolution prompts and automatic summary posting to PR
  • Works after a PR is opened and before merge to enforce quality gates with configurable depth (light/full)

Quick Start

Trigger a review on a PR to initiate automated verification and receive a summary of results.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR reviews and acceptance criteria verification before merge on GitHub?

Automating PR reviews is achieved by triggering predefined scripts that coordinate multi-perspective checks and acceptance criteria verification on GitHub pull requests before merge, posting automatic summaries.

Can I trigger automated code reviews after pushing code to a GitHub PR?

Yes, automated code reviews can be triggered after code is pushed to a GitHub PR. The process initiates verification steps, resolves identified issues, and posts a summary to the pull request before merge.

Does automated PR verification support configurable review depth for different checks?

Automated PR verification supports configurable depth, allowing you to select light or full review modes. This enforces quality gates by adjusting the intensity of multi-perspective checks and acceptance criteria validation.

What is the best way to enforce quality gates and run multi-perspective PR reviews?

The best way to enforce quality gates is by orchestrating multi-perspective PR reviews through predefined scripts. This method automatically validates acceptance criteria and posts summary results directly to GitHub.

Do I need GitHub access to automate issue resolution prompts and PR summary posting?

Yes, GitHub access is required to automate issue resolution prompts and PR summary posting. The automated review process relies on this access to read PR changes and post verification summaries back.

Why use automated multi-perspective reviews instead of manual PR checks?

Automated multi-perspective reviews reduce manual toil and speed up quality checks by coordinating acceptance criteria verification and issue resolution prompts automatically, ensuring consistent validation before merging code.