review

Analyze branch diffs for SQL safety and trust boundary issues.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Intension-us/attention-diagnostic --skill review-intension-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Intension-us/attention-diagnostic/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/Intension-us/attention-diagnostic --skill review-intension-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review helps ensure code changes are safe and align with project policies by analyzing diffs against the base branch for SQL safety, LLM trust boundaries, conditional side effects, and other structural issues. It also proactively suggests improvements before merging.

Core Features & Use Cases

  • Analyzes PR diffs for SQL safety, trust boundary violations, conditional side effects, and other structural issues.
  • Suggests proactive checks and routing guidance when a diff is ready to merge.
  • Useful for teams performing pre-landing reviews, code reviews, or diff checks in CI/CD workflows.

Quick Start

Provide a pre-landing PR review by analyzing the branch diff against the base and surface SQL safety, LLM trust boundary issues, and structural risks before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze a PR diff for SQL safety and LLM trust boundary issues?

To analyze a PR diff for SQL safety and LLM trust boundary issues, run a pre-landing review against the base branch. This surfaces conditional side effects and structural risks before merging by enforcing policy-aware checks on the code changes.

What is pre-landing PR review for safe code diffs?

Pre-landing PR review for safe code diffs is the process of analyzing branch changes against the base branch to surface SQL safety issues, LLM trust boundary violations, and conditional side effects before merging. It provides actionable feedback and suggests improvements.

Can I use automated diff analysis to enforce policy-aware checks in CI/CD workflows?

Yes, you can use automated diff analysis to enforce policy-aware checks in CI/CD workflows. The review process integrates with gstack tooling to provide structured feedback, surfacing actionable risks and routing guidance when a diff is ready to merge.

How do I run a pre-landing review using shell scripts and gstack tooling?

You can run a pre-landing review by triggering the /review workflow or saying "review this PR". The process uses shell scripts and integrates with gstack tooling to analyze the diff and proactively suggest improvements before landing changes.

What are the limitations of automated diff analysis for catching conditional side effects?

Automated diff analysis for catching conditional side effects focuses specifically on structural issues, SQL safety, and LLM trust boundaries. It functions as a pre-landing check to surface actionable feedback, but requires a defined base branch diff to execute properly.