skills.rest
yolopunk
yolopunkCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze diffs against the base branch for SQL safety, LLM trust boundary, and side-effect issues.

Updated Apr 6, 2025
Search Tags:#llm#quality#sql#review#trust#diff
One-click install
npx skills add https://github.com/yolopunk/jedi --skill review-yolopunk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/yolopunk/jedi --skill review-yolopunk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch to surface SQL safety violations, LLM trust boundary issues, and conditional side effects that could affect correctness, security, or deployment outcomes.

Core Features & Use Cases

  • Detects SQL-related risks in diffs (e.g., interpolation without parameterization, unsafe query patterns).
  • Flags LLM trust boundary issues, such as leaking prompts or unsafe data handling.
  • Identifies scope drift and missing requirements in PRs, proposing concrete remediation steps.
  • Supports pre-landing reviews, code reviews, and PR validations to prevent merge-time defects.

Quick Start

Run a PR review by providing the branch and diffs to surface actionable findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I detect SQL injection risks in a pull request diff?▼

To detect SQL injection risks in a pull request diff, analyze the changes against the base branch to surface unsafe query patterns like string interpolation without parameterization. This identifies SQL safety violations and provides concrete remediation steps to prevent merge-time defects.

What are LLM trust boundary issues in code reviews?▼

LLM trust boundary issues in code reviews involve leaking prompts or handling unsafe data when integrating language models. Identifying these issues during pre-landing PR reviews flags potential security vulnerabilities and scope drift before deployment.

How can I automate pre-landing checks for conditional side effects?▼

Automate pre-landing checks for conditional side effects by analyzing diffs against the base branch to flag scope drift and missing requirements. This surfaces deployment risks and proposes actionable fixes including edge-case handling and validation steps.

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

Pre-landing PR review works without external dependencies by directly analyzing the branch and diffs provided. It surfaces actionable findings for SQL safety, LLM trust boundaries, and conditional side effects to prevent merge-time defects.

What is the best way to prevent merge-time defects from unsafe query patterns?▼

The best way to prevent merge-time defects from unsafe query patterns is running pre-landing code reviews that analyze diffs for SQL interpolation risks. This flags safety violations and provides concrete fixes before the code merges.

Related Skills

Explore More Software Engineering Skills→
arowinskiarowinski

pr

Create pull requests with titles and template-aligned bodies from git diffs.

Community
Intermediate
Andy-HNUAndy-HNU

review

Analyzes PR diffs for SQL safety, LLM trust boundary violations, conditional side effects, and other structural risks.

Community
Advanced
ROLLED740ROLLED740
1

springboot-verification

Automates Spring Boot build, static analysis, test coverage, security scan, and diff review for Maven/Gradle CI pipelines.

Community
Advanced
jiten-singh-shahijiten-singh-shahi
13

security-scan

Audit Claude Code configuration files for security vulnerabilities and emit JSON findings.

Community
Intermediate