review

Analyzes diffs against the base branch for SQL safety, trust boundary, and side-effect issues.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/anishs1207/agentic-cli --skill review-anishs1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/anishs1207/agentic-cli/tree/main/.agents/skills/gstack-review
Command: npx skills add https://github.com/anishs1207/agentic-cli --skill review-anishs1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff" to proactively suggest when the user is about to merge or land code changes.

Core Features & Use Cases

  • Detects structural issues in diffs and surfaces actionable recommendations.
  • Analyzes SQL safety, trust boundaries, and side effects to reduce risky merges.
  • Use Case: when preparing a PR, run the review to catch potential problems before merge.

Quick Start

Run the review on the current pull request by diffing against the base branch to surface issues and suggested fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR reviews to catch SQL safety issues before merging?

Automate PR reviews by analyzing diffs against the base branch to identify SQL safety issues and provide concrete mitigations. This process proactively surfaces structural problems and risky merges before code lands.

What is an AI-aware diff analysis for pre-landing code reviews?

AI-aware diff analysis checks code changes against the base branch to detect LLM trust boundary violations, conditional side effects, and SQL safety issues. It provides actionable recommendations based on repository context to reduce risky merges.

How do I check my diff for LLM trust boundary violations?

Check your diff by running a pre-landing review that analyzes changes against the base branch for LLM trust boundary violations. The review surfaces structural issues and suggests concrete fixes based on the repository context.

When do I need to run an automated diff check for conditional side effects?

Run an automated diff check when preparing a pull request to catch conditional side effects before merge. Analyzing the diff against the base branch identifies structural issues and provides actionable recommendations to ensure safe landing.

Can I use diff analysis across multiple codebases and tools?

Yes, you can apply diff analysis across codebases using multiple tools to perform pre-landing reviews and diff checks. It identifies SQL safety, LLM trust boundaries, and conditional side effects regardless of the specific repository context.

What's the best way to review a PR for SQL safety and LLM trust boundaries?

The best way to review a PR is to analyze the diff against the base branch to detect SQL safety issues and LLM trust boundary violations. This provides concrete recommendations and mitigations based on the specific diff and repository context.