skills.rest
tsensei
tsenseiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Analyze diffs for SQL safety, LLM trust boundary violations, and structural risks.

3|3|Updated Mar 26, 2026
Search Tags:#llm#safety#quality#sql#review#diff#pr
One-click install
npx skills add https://github.com/tsensei/ReelMistri --skill review-tsensei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/tsensei/ReelMistri/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/tsensei/ReelMistri --skill review-tsensei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews identify SQL safety issues, LLM trust boundary violations, and other structural issues in diffs before merging.

Core Features & Use Cases

  • Scan diffs for SQL safety, LLM boundary violations, and conditional side effects.
  • Proactively suggest improvements and next steps for merge-readiness.
  • Use Case: When reviewing a PR that touches data handling or model prompts, receive a structured risk assessment.

Quick Start

Run the review on your current branch to pre-screen the diff against the base branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a diff for SQL safety issues before merging?▼

To check a diff for SQL safety issues before merging, you can run a pre-landing review that analyzes your branch differences to identify structural risks and provide merge-readiness guidance.

What are LLM trust boundary violations in code reviews?▼

LLM trust boundary violations in code reviews occur when model prompts or data handling bypass security safeguards, which pre-landing diff scans identify to proactively suggest improvements before merge.

How do I assess merge-readiness for a PR with database changes?▼

To assess merge-readiness for a PR with database changes, run a diff check against your base branch to scan for SQL safety issues, conditional side effects, and structural risks.

Can I get automated risk assessments for PRs touching model prompts?▼

Yes, you can receive structured risk assessments for PRs touching model prompts by running pre-landing reviews that scan diffs for LLM boundary violations and conditional side effects.

Does pre-landing code review work without external dependencies?▼

Yes, pre-landing code review works without external dependencies because it directly analyzes your current branch diff against the base branch to identify structural risks.

When should I use a pre-landing PR review instead of post-merge checks?▼

You should use a pre-landing PR review instead of post-merge checks when you need to proactively catch SQL safety issues, LLM trust boundary violations, and conditional side effects before they enter the main branch.

Related Skills

Explore More Software Engineering Skills→
chriswesttchriswestt

review

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

Community
Advanced
matteocervellimatteocervelli
25

pr-merge

Validate CI/CD checks, reviews, conflicts, then merge GitHub PRs via squash, merge, or rebase.

Community
Basic
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate