skills.rest
gfires
gfiresCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze pull request diffs for structural risks and side effects.

Updated Aug 23, 2026
Search Tags:#review#code-quality#pull-request#diff-analysis#gstack#pre-landing#scope-drift
One-click install
npx skills add https://github.com/gfires/motion-analysis --skill review-gfires
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/gfires/motion-analysis/tree/main/review
Command: npx skills add https://github.com/gfires/motion-analysis --skill review-gfires

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines pre-landing PR review by analyzing diffs against the base branch to surface structural issues that tests do not catch and align changes with intent.

Core Features & Use Cases

  • Automates checks for SQL safety, contract boundaries, and potential side effects in diffs.
  • Flags missing test coverage and scope drift, ensuring changes align with the PR description.
  • Generates actionable guidance and concrete next steps to help reviewers move merges forward safely.

Quick Start

Trigger /review on this branch to start the automated pre-landing PR analysis.

Frequently Asked Questions about review

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

FAQPage Schema
How do I catch structural risks in a pull request that tests miss?▼

To catch structural risks in a pull request that tests miss, analyze the PR diff against the base branch to surface scope drift, data safety issues, and potential side effects. This safety-first approach returns actionable guidance and recommended next steps to ensure a clean merge.

What is scope drift in a PR and how do I check for it?▼

Scope drift in a PR occurs when changes deviate from the original intent. You can check for scope drift by analyzing the diff against the base branch and aligning the modifications with the PR description to flag unrelated or unintended structural changes.

How do I automate SQL safety and contract boundary checks in a diff?▼

Automate SQL safety and contract boundary checks in a diff by applying a pre-landing review process that analyzes the current changes against the base branch. This surfaces potential side effects and structural issues automatically before merging.

Does automated diff analysis work for pre-landing code review without dependencies?▼

Yes, automated diff analysis for pre-landing code review works without external dependencies. It analyzes the current branch diff against the base branch to identify structural risks, missing test coverage, and scope drift directly.

When do I need pre-landing PR analysis for my codebase?▼

You need pre-landing PR analysis when you want to ensure changes align with intent before merging. It is essential for surfacing structural issues like SQL safety risks, contract boundary violations, and potential side effects that automated tests do not catch.

Related Skills

Explore More Software Engineering Skills→
AkbarDevopAkbarDevop

review

Identify production-risk findings in a code diff before merging.

Community
Advanced
sunnypatneedisunnypatneedi
11

code-review

Review codebases for defects, security gaps, and maintainability concerns.

Community
Basic
ManzuetiManzueti

health

Wrap project tools to compute a weighted codebase health score.

Community
Advanced
aarushlohitaarushlohit

zen-review

Review pull request changes for correctness, security, performance, and quality.

Community
Advanced