skills.rest
louisfghbvc
louisfghbvcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

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

4|1|Updated Sep 13, 2023
Search Tags:#review#code-review#pull-request#diff-analysis#pre-merge#LLM-safety#SQL-safety
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill review-louisfghbvc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/review
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill review-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review analyzes diffs against the base branch to surface SQL safety risks, potential LLM trust boundary violations, and other structural issues before merging.

Core Features & Use Cases

  • Analyzes diffs for potential SQL injection risks, unsafe queries, and data leakage in PRs.
  • Checks for trust boundary violations and unconditional side effects introduced by changes.
  • Proactively suggests improvements and remediation steps to reduce merge risk during pre-merge reviews.

Quick Start

Run the review on the current branch to surface issues in the diff before merging.

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 for SQL injection risks before merging?▼

To check a pull request for SQL injection risks before merging, analyze the diff against the base branch to surface unsafe queries and data leakage. This pre-landing review proactively suggests remediation steps to ensure safe merges.

What is pre-landing code review and how does it handle LLM trust boundaries?▼

Pre-landing code review analyzes diffs to identify potential LLM trust boundary violations and unconditional side effects. It ensures changes do not introduce unsafe operations before merging into the base branch.

How do I analyze a diff against the base branch for structural issues?▼

Analyze a diff against the base branch for structural issues by running a pre-merge review workflow. This process surfaces SQL safety risks, LLM trust boundary violations, and provides actionable remediation guidance.

Can I use automated diff analysis to reduce merge risk in my workflow?▼

Yes, you can use automated diff analysis to reduce merge risk by proactively suggesting improvements during pre-merge reviews. It surfaces potential data leakage and structural issues before changes land.

Does pre-merge code review work without additional dependencies?▼

Pre-merge code review works without additional dependencies to analyze diffs against the base branch. It directly surfaces SQL safety risks and LLM trust boundary violations to support merge decisions.

Related Skills

Explore More Software Engineering Skills→
YaugourtYaugourt
2

review

Analyze code diffs for SQL safety, trust boundary, and side effect issues.

Community
Advanced
sergicalsergical

sentry-pr-code-review

Parse Sentry bot comments in GitHub PRs to extract issues and suggested fixes.

Community
Advanced
aporto-techaporto-tech

gstack-review

Analyze code diffs for SQL safety and LLM trust boundary violations.

Official
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

dry-run

Simulate command side effects without executing them.

Community
Advanced