skills.rest
bajajvinamr
bajajvinamrCOMMUNITY
Explore all skills by this author →
Website𝕏@axios_iiitlGitHub

review

Analyze PR diffs for SQL safety, trust boundary violations, and side effects.

Updated Apr 1, 2026
Search Tags:#review#todos#pr-review#plan-mode#diff-analysis#prelanding#scope-drift
One-click install
npx skills add https://github.com/bajajvinamr/little-wins --skill review-bajajvinamr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/bajajvinamr/little-wins/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/bajajvinamr/little-wins --skill review-bajajvinamr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-heavy PRs can hide structural issues that slip past tests. This Skill analyzes the PR diff against the base branch to surface SQL safety concerns, LLM trust boundary violations, and conditional side effects before merging.

Core Features & Use Cases

  • Detects scope drift by comparing the current diff to the PR description and TODOS.md intent.
  • Validates plan-mode state and project routing signals to guide reviewers.
  • Generates a structured, action-oriented review plan that you can follow or export.

Quick Start

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

Frequently Asked Questions about review

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

FAQPage Schema
How do I catch SQL safety issues in a PR diff before merging?▼

Pre-landing PR review analyzes your diff against the base branch to surface SQL safety concerns before merging. It detects structural risks like conditional side effects that often slip past automated tests in diff-heavy pull requests.

What is scope drift detection in code review?▼

Scope drift detection in code review compares the current pull request diff to the PR description and TODOS.md intent. This validates that the changes align with the planned scope and project routing signals before the branch lands.

How do I check for LLM trust boundary violations in a pull request?▼

You can check for LLM trust boundary violations by running a pre-landing diff analysis on your feature branch. The review process surfaces these structural risks by analyzing the code changes against the base branch before merging.

Can I automate pre-landing code review for conditional side effects?▼

Yes, pre-landing code review can be automated by running the /review workflow on your feature branch. It analyzes the diff for conditional side effects and generates a structured, action-oriented review plan to guide the reviewer.

Does pre-landing PR review work with plan-mode state and TODOS.md?▼

Pre-landing PR review validates plan-mode state and reads TODOS.md alignment to guide reviewers. It uses these project routing signals to detect scope drift and produce a structured, ready-to-act review output for the diff.

What are the limitations of diff analysis for pre-landing code review?▼

Diff analysis for pre-landing code review focuses strictly on structural risks like SQL safety and LLM trust boundaries. It does not replace runtime testing but serves as an early detection layer for issues hidden within diff-heavy pull requests.

Related Skills

Explore More Software Engineering Skills→
studyzystudyzy

review

Analyze PR diffs against the base branch for structural issues.

Community
Advanced
nuurpronuurpro
1

review

Analyze pull request diffs for SQL safety, LLM trust boundary violations, and side effects.

Community
Advanced
viraatdasviraatdas

review

Review branch diffs for scope drift and missing requirements.

Community
Advanced
BradliebsBradliebs

review

Analyze PR diffs against the base branch for SQL safety and LLM trust boundary issues.

Community
Advanced