skills.rest
Jesse-L-M
Jesse-L-MCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze PR diffs against the base branch for structural issues.

Updated Mar 27, 2026
Search Tags:#automation#security#quality-assurance#pr-review#diff-analysis#llm-trust
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill review-jesse-l-m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill review-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often introduce structural issues that tests don't cover. This skill analyzes the diff between the PR and the base branch to surface gaps in data safety, trust boundaries, and plan integrity before merging.

Core Features & Use Cases

  • Checks for SQL safety, race conditions, LLM trust boundary violations, shell injection risks, and enum completeness across the diff.
  • Identifies conditional side effects and plan-routing requirements to prevent regressions and improve review quality.
  • Generates a structured, actionable report that guides remediation and documents telemetry for auditing.

Quick Start

Provide your PR diff to this skill to pre-flight changes before land.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check PR diffs for SQL safety and race conditions before merging?▼

To check PR diffs for SQL safety and race conditions before merging, analyze the code changes against the base branch to surface structural issues not captured by tests. This evaluates data safety, trust boundaries, and plan integrity to guide remediation.

What is LLM trust boundary analysis in automated code review?▼

LLM trust boundary analysis in automated code review identifies violations where untrusted inputs cross into LLM processing logic. It evaluates these trust boundaries across PR diffs and plan files to prevent security regressions before merging.

How do I detect shell injection risks and conditional side effects in a pull request?▼

To detect shell injection risks and conditional side effects in a pull request, analyze the diff against the base branch to surface plan-critical concerns. This generates a structured report with suggested fixes and telemetry for auditing.

Can I use automated diff analysis to find enum completeness issues not covered by tests?▼

Yes, you can use automated diff analysis to find enum completeness issues not covered by tests. By evaluating the PR diff against the base branch, it surfaces structural gaps in data safety and plan routing requirements before landing code.

What's the best way to generate structured remediation reports for pre-landing PR reviews?▼

The best way to generate structured remediation reports for pre-landing PR reviews is to analyze PR diffs for SQL safety, LLM trust boundaries, and conditional side effects. This outputs actionable findings with suggested fixes and telemetry to guide remediation.

Related Skills

Explore More Software Engineering Skills→
aimasteraccaimasteracc
46

review

Analyze branch diffs for SQL safety, trust boundaries, and side effects.

Community
Advanced
TobiasPerryTobiasPerry

review

Analyze branch diffs for SQL safety, LLM trust boundaries, and side effects.

Community
Advanced
carson-sweetcarson-sweet
6

Code Testing

Execute test suites, mutation testing, security audits, and PR pre-checks.

Community
Advanced
ToanPV90ToanPV90

sast-scanning

Detects source code vulnerabilities via static analysis with JSON/SARIF outputs.

Community
Advanced