review

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

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill review-sanskarbasnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sanskarbasnet/fstack/tree/main/review
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill review-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews often miss subtle SQL safety issues, LLM trust boundary violations, and conditional side effects that can introduce risks when merging changes. This skill analyzes diffs against the base branch to surface these issues and guide safer merges.

Core Features & Use Cases

  • SQL safety scrutiny: detects risky interpolations, unsafe queries, or potential injections in diffs.
  • LLM trust boundary checks: flags prompts that could leverage or leak system prompts or bypass safety filters.
  • Conditional side effects awareness: highlights diffs that could trigger unintended behavior depending on context.
  • Proactive merge guidance: suggests mitigations and next steps to keep PRs merge-ready.

Quick Start

Provide the PR diff and a brief description, and ask me to perform a pre-landing review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a pull request diff for SQL injection risks before merging?

To check a pull request diff for SQL safety, analyze the diff against the base branch to detect risky interpolations, unsafe queries, and potential injections. This pre-landing review surfaces SQL vulnerabilities and provides actionable mitigations to ensure a safe merge.

What is an LLM trust boundary violation in code review?

An LLM trust boundary violation occurs when prompts could leverage or leak system prompts or bypass safety filters. Code review detects these risks by analyzing PR diffs against the base branch, flagging potentially dangerous prompt manipulations before merging changes.

How do I perform a pre-landing review on my code diff?

Perform a pre-landing review by providing the PR diff and a brief description. The review analyzes the diff against the base branch to identify SQL safety issues, LLM trust boundary violations, and conditional side effects, generating reviewer notes and mitigation guidance for a safe merge.

Can I detect conditional side effects in a pull request diff?

Yes, you can detect conditional side effects by analyzing PR diffs against the base branch. This review highlights code changes that could trigger unintended behavior depending on context, helping prevent subtle issues before landing your code.

Does this code review skill integrate with Claude Code tools?

Yes, this code review skill integrates with Claude Code tools to support typical PR review scenarios. It analyzes diffs against the base branch for SQL safety, LLM trust boundaries, and conditional side effects to generate actionable merge guidance.

What is the best way to surface unintended side effects in a PR?

The best way to surface unintended side effects in a PR is to analyze the code diff against the base branch. This identifies conditional side effects and LLM trust boundary violations, providing actionable reviewer notes and mitigations to keep the pull request merge-ready.