unity-review-general

Post a final APPROVE or REQUEST_CHANGES decision on GitHub pull requests after specialist reviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cuozg/oh-my-unity --skill unity-review-general
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-review-general
Source: https://github.com/cuozg/oh-my-unity/tree/main/skills/unity-review-general
Command: npx skills add https://github.com/cuozg/oh-my-unity --skill unity-review-general

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates and enforces a single, definitive PR decision (APPROVE or REQUEST_CHANGES) after all specialist reviews have completed, preventing premature merges.

Core Features & Use Cases

  • Enforces a final quality gate on PRs after reviews across code, architecture, and assets.
  • Aggregates metadata from PR, review history, and file changes to inform the final decision.
  • Use case: teams that require a single, auditable merge decision after multi-discipline reviews.

Quick Start

Trigger the review on a PR and provide a final APPROVE or REQUEST_CHANGES decision after evaluating all criteria.

Frequently Asked Questions about unity-review-general

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

FAQPage Schema
How do I enforce a final approval gate on GitHub pull requests after specialist reviews?

A final approval gate on GitHub pull requests enforces a single, definitive APPROVE or REQUEST_CHANGES decision after all specialist reviews are complete, preventing premature merges by aggregating PR metadata, file changes, and review history.

What is a unified code review quality gate and when do I need it?

A unified code review quality gate is a single checkpoint that evaluates security, correctness, testing, performance, and documentation across code, architecture, and assets. You need it when your team requires an auditable merge decision after multi-discipline reviews.

How to automate a final PR decision using the GitHub API?

Automating a final PR decision using the GitHub API involves fetching pull request metadata, loading changed files, assessing code quality criteria, and then posting a final review decision via the API to act as a sole approval gate.

Can I use an automated code review gate for multi-discipline pull requests?

Yes, you can use an automated code review gate for multi-discipline pull requests. It applies across code, architecture, and assets, aggregating metadata from all specialist reviews to inform a single unified merge decision.

Why do I need a sole PR approval gate if I already have automated code reviews?

A sole PR approval gate is needed because individual automated code reviews focus on specific domains. The gate aggregates those specialist reviews and enforces a single, definitive decision to prevent premature merges before all criteria are fully evaluated.