skills.rest
rkumar261
rkumar261COMMUNITY
Explore all skills by this author →
𝕏@r_kumar261GitHub

review

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

1|Updated Dec 23, 2025
Search Tags:#code-review#pull-request#pr-review#diff-analysis#sql-safety#llm-trust#pre-landing
One-click install
npx skills add https://github.com/rkumar261/studio-cast --skill review-rkumar261
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/rkumar261/studio-cast/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/rkumar261/studio-cast --skill review-rkumar261

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review analyzes diffs to surface structural and trust-boundary issues that might cause risky merges.

Core Features & Use Cases

  • Analyzes diffs between PR and base branch for SQL safety, trust boundary violations, and side effects.
  • Proactively surfaces actionable findings to guide reviewers and engineers.
  • Supports standard PR workflows by highlighting risks and recommended fixes before merge.
  • Use Case: When a PR touches database queries or AI prompts, this skill reveals potential issues before landing.

Quick Start

Ask me to perform a pre-landing PR review on the current diff to surface SQL safety, trust boundary, and side-effect issues before merging.

Frequently Asked Questions about review

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

FAQPage Schema
What is pre-landing code review and how does diff analysis work?▼

Pre-landing code review analyzes the current PR diff against the base branch to identify SQL safety issues, trust boundary violations, and potential side effects. Diff analysis surfaces actionable findings to prevent risky merges before landing.

How do I perform a PR review to check for SQL safety and trust boundary violations?▼

You can perform a PR review by requesting a pre-landing check on the current diff. The analysis evaluates the changes against the base branch to detect SQL safety risks, trust boundary violations, and side effects, suggesting fixes to guide reviewers.

Does pre-landing diff analysis work for standard pull request workflows?▼

Yes, pre-landing diff analysis supports standard PR workflows by highlighting structural risks and recommended fixes before merge. It evaluates edge cases and surfaces actionable findings to help engineers prevent risky merges.

When do I need to run a pre-landing PR review?▼

You need a pre-landing PR review when a pull request touches database queries or AI prompts. Running diff analysis before merging reveals potential SQL safety issues, trust boundary violations, and side effects.

What's the best way to identify side effects in a pull request before merging?▼

The best way to identify side effects is analyzing the PR diff against the base branch. This pre-landing review evaluates edge cases, detects potential side effects and trust boundary violations, and suggests fixes to prevent risky merges.

Why should I not merge a pull request without checking for trust boundary issues?▼

Merging without checking for trust boundary issues risks introducing LLM trust violations and side effects. Pre-landing PR review analyzes the diff to surface these structural risks and suggests fixes to prevent risky merges before landing.

Related Skills

Explore More Software Engineering Skills→
SeaLion-hubSeaLion-hub

review

Analyze pull request diffs for SQL safety, trust boundaries, and side effects.

Community
Advanced
ZhangHanDongZhangHanDong
45

code-review

Analyze GitHub pull request diffs and generate review comments.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

review

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

Community
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic