skills.rest
SakshamKandel
SakshamKandelCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze diffs against the base branch for SQL safety and structural issues.

Updated Apr 24, 2026
Search Tags:#review#code-quality#pull-request#trust-boundaries#diff-analysis#gstack#sql-safety
One-click install
npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill review-sakshamkandel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/SakshamKandel/Salt-Route-Consulting-/tree/main/.agents/skills/review
Command: npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill review-sakshamkandel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues to surface risks early in PR reviews.

Core Features & Use Cases

  • Provides automated diff analysis for code reviews focusing on safety, trust boundaries, and potential side effects.
  • Suggests actionable improvements and risk mitigations during pre-landing reviews.
  • Works with triggers like "review this pr" or "code review" to guide engineers toward high-quality merges.

Quick Start

Ask the assistant to review the PR and return a concise report with issues, risks, and recommended actions.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request for SQL safety and trust boundary violations?▼

To review a pull request, analyze the diff against the base branch to surface SQL safety issues, LLM trust boundary violations, and conditional side effects, providing recommended actions for a safe merge.

What is automated diff analysis in pre-landing code reviews?▼

Automated diff analysis evaluates changes against a base branch to detect SQL safety risks, LLM trust boundary violations, and conditional side effects before merging to guide high-quality merges.

Can I use this code review approach to detect conditional side effects in my diff?▼

Yes, you can detect conditional side effects by analyzing your diff against the base branch to surface structural issues, risks, and recommended actions during the pre-landing pull request review.

What's the best way to guide a safe merge when reviewing a PR?▼

The best way to guide a safe merge is to analyze the diff for SQL safety and trust boundary violations, surfacing issues, risks, and recommended actions to ensure high-quality code integration.

Do I need specific tooling to analyze LLM trust boundaries in a pull request?▼

You need available tooling such as Read, Write, Edit, Grep, Glob, Agent, and WebSearch, along with project context, to reason about changes and analyze LLM trust boundaries during a pull request review.

What are the limitations of automated diff analysis for code quality?▼

Automated diff analysis relies on available tooling and project context to reason about changes with safety and completeness, meaning its effectiveness is bounded by the available tools and provided project context.

Related Skills

Explore More Software Engineering Skills→
AndrewLi0420AndrewLi0420

review

Analyze pull request diffs for SQL safety and trust boundary issues.

Community
Advanced
s977043s977043
2

code-review

Analyze pull-request diffs to identify security, performance, quality, and test risks.

Community
Basic
23000311472300031147

review

Analyze pull request diffs for SQL safety and trust boundary issues.

Community
Advanced
zz8011zz8011

review

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

Community
Intermediate