review

Analyze diffs for SQL safety, trust boundary, and side-effect risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, and conditional side effects before merging. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)

Core Features & Use Cases

  • Automated checks across diffs for data-safety, prompt-injection risks, and side-effect analysis.
  • Proactive recommendations and routing to next steps when code changes are about to merge.
  • Use Case: When asked to review a PR, the skill scans the diff and highlights critical risk areas, suggesting fixes or routing to plan review.

Quick Start

Review the current PR diff and surface critical risks to guide a safe merge.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff for SQL safety issues before merging?

Pre-landing PR review analyzes your diff against the base branch to automatically surface SQL safety issues. It scans the code changes to highlight critical risk areas and suggests fixes before you merge.

What is LLM trust boundary violation detection in code review?

LLM trust boundary violation detection identifies prompt-injection risks within your code changes. Pre-landing PR review scans diffs to proactively surface these violations and other conditional side effects before merging.

How can I check my diff for conditional side effects before landing code?

You can check your diff for conditional side effects by running a pre-landing PR review. The skill implements structured checks across the diff against the base branch to proactively identify side effects and guide safe merge decisions.

Does this code review skill work across multiple repositories?

Yes, the pre-landing PR review is applicable to pull requests, code reviews, and diffs across repositories. It analyzes changes against the base branch before merging to ensure consistent data-safety and risk-detection checks.

What is the best way to automate merge decision guidance for pull requests?

The best way to automate merge decision guidance is to use a pre-landing PR review skill that implements structured checks. It proactively routes next steps and recommends actions when code changes are about to merge based on detected risks.