skills.rest
sobhanashine
sobhanashineCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyzes pull-request diffs for SQL safety and LLM trust boundary violations.

1|Updated May 12, 2026
Search Tags:#code quality#code analysis#PR review#SQL safety#LLM trust boundary
One-click install
npx skills add https://github.com/sobhanashine/nazarato --skill review-sobhanashine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sobhanashine/nazarato/tree/main/.claude/skills/review
Command: npx skills add https://github.com/sobhanashine/nazarato --skill review-sobhanashine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, WebSearch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the review of pull requests for SQL safety, LLM trust boundary violations, and other structural issues, reducing manual effort and increasing code quality.

Core Features & Use Cases

  • Automated PR Review: Analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Use Case: Use this Skill when asked to "review this PR", "code review", "pre-landing review", or "check my diff" to proactively suggest issues and improvements before merging or landing code changes.

Quick Start

Run the review skill to analyze the current PR for potential issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR review for SQL safety and LLM trust boundary violations?▼

Automated PR review for SQL safety and LLM trust boundary violations analyzes pull request diffs against a base branch to detect structural issues. It proactively suggests improvements before merging code changes.

What is an LLM trust boundary violation in code analysis?▼

An LLM trust boundary violation in code analysis occurs when untrusted model inputs cross security limits unchecked. Automated PR review detects these violations by analyzing code diffs for potential boundary breaches.

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

Check your diff for conditional side effects by running an automated pre-landing review. This analyzes pull request changes against the base branch to identify structural issues and suggest fixes before merging.

Does automated code review work with Bash and Grep for diff analysis?▼

Automated code review works with Bash, Grep, Read, and Glob to process code changes. These dependencies enable the analysis of pull request diffs for SQL safety and structural code quality issues.

When do I need automated code review for SQL safety?▼

You need automated code review for SQL safety when preparing to merge or land code changes. It analyzes pull request diffs to detect SQL safety risks, LLM trust boundary violations, and conditional side effects.

What is the best way to run a pre-landing review on a pull request?▼

The best way to run a pre-landing review is to use an automated review Skill that analyzes current pull request diffs. It detects SQL safety issues, LLM trust boundary violations, and structural problems.

Related Skills

Explore More Software Engineering Skills→
chcardozchcardoz

create-pr

Push a local Git branch and create a GitHub pull request.

Community
Intermediate
abhishekmmgnabhishekmmgn

review

Analyze PR diffs for SQL safety and trust boundary violations.

Community
Advanced
nicolanoviellnicolanoviell
2

code-review

Review code changes for bugs, style issues, and best practices.

Community
Intermediate
lexicalninjalexicalninja
2

security-scanner

Scan codebases for security vulnerabilities and generate structured remediation reports.

Community
Advanced