review

Analyze diffs and PR context for structural, data-safety, and quality issues.

Updated Mar 28, 2026

Search Tags:#automation #LLM #review #diff #code-quality #pull-request #data-safety

Ready to run

npx skills add https://github.com/24601/gastack-pre-fork --skill review-24601

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/24601/gastack-pre-fork/tree/main/review
Command: npx skills add https://github.com/24601/gastack-pre-fork --skill review-24601

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams catch structural issues, data-safety risks, and quality gaps in PRs before merging by evaluating diffs and PR context.

Core Features & Use Cases

Diff-based quality checks for pre-landing reviews
LLM trust boundary validation and SQL safety checks
Plan alignment and scope drift detection to keep PRs focused

Quick Start

Run the /review workflow on your current branch to start the pre-landing review.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate pull-request reviews to catch data-safety risks before merging?▼

Automating pull-request reviews analyzes branch diffs and PR context to surface data-safety risks before merging. The process evaluates SQL safety, validates LLM trust boundaries, and logs evidence to ensure edge cases are addressed.

What is the best way to detect scope drift and maintain code-quality in pre-landing reviews?▼

Detecting scope drift during pre-landing reviews evaluates diffs against the original plan to keep PRs focused. It checks structural code-quality issues and ensures test coverage matches the PR context before landing.

Does automated code review work without adding external dependencies or components?▼

Automated code review requires no external dependencies or components to function. It operates directly within your repository environment to evaluate diffs and structural issues, provided you have repository access.

How do I run a pre-merge PR review workflow on my current branch?▼

To run a pre-merge PR review, execute the /review workflow on your current branch. The system analyzes the diff, checks plan alignment, and outputs actionable items with evidence for reviewers.

Why does my pull-request review need to validate the LLM trust boundary?▼

Validating the LLM trust boundary during a pull-request review identifies data-safety risks before merging. It ensures the LLM integration respects defined limits and logs evidence to guide reviewers on structural issues.

When should I not rely on automated diff analysis for code review?▼

Automated diff analysis for code review should not replace human judgment for complex business logic. It surfaces structural, data-safety, and quality gaps using evidence, but reviewers must still verify contextual correctness.