Verified:GitHub

review

Name: review
Availability: InStock
Author: GenEd

Analyze pull-request diffs for defects and scope drift in GitHub or GitLab.

Updated Mar 30, 2026

Search Tags:#github #review #gitlab #code-review #pull-request #diff-analysis #merge-safety

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill review-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/review
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill review-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch structural, safety, and scope problems in a pull request before it lands, so you do not ship avoidable defects or accidental blast radius.

Core Features & Use Cases

Scope drift detection: Checks whether the branch actually delivered the requested change and flags unrelated edits.
Risk review: Looks for SQL safety, race conditions, trust-boundary problems, enum completeness gaps, and other correctness issues that tests may miss.
Use case: Use it when you are about to merge a branch and want a reviewer to point at the exact file and line that needs attention.

Quick Start

Use the review skill to compare this branch against the base branch and tell me exactly what is broken or out of scope.

Frequently Asked Questions about review

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

FAQPage Schema

How do I catch pull-request issues before merging a branch?▼

To catch pull-request issues before merging, you analyze branch diffs for pre-landing defects. This Skill compares your branch against the base to flag structural problems, SQL safety risks, and scope drift before they land.

What is scope drift detection in a code review?▼

Scope drift detection in a code review checks whether a pull-request branch actually delivered the requested change. It flags unrelated edits by analyzing file-level context from the diff to prevent accidental blast radius before merging.

Can I run a merge-readiness check on a GitHub pull request?▼

Yes, you can run a merge-readiness check on a GitHub pull request. The Skill applies to GitHub and GitLab repositories, requiring branch comparison to perform diff analysis and identify exact files needing attention before merge.

How do I find race conditions and SQL safety issues in a diff?▼

To find race conditions and SQL safety issues in a diff, you apply issue classification across trust boundaries and concurrency. This Skill analyzes pull-request diffs for correctness issues that standard tests may miss before landing.

What is the best way to audit branch risk before a merge?▼

The best way to audit branch risk before a merge is to perform a diff analysis covering enum completeness gaps and trust-boundary problems. This Skill classifies these correctness issues by comparing branches and reviewing file-level context.