skills.rest
effiraid
effiraidCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze PR diffs for SQL safety, LLM trust boundaries, and structural risks.

Updated Aug 23, 2026
Search Tags:#review#code-quality#diff-analysis#gstack#sql-safety#llm-trust
One-click install
npx skills add https://github.com/effiraid/reflix-nextjs --skill review-effiraid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/effiraid/reflix-nextjs/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/effiraid/reflix-nextjs --skill review-effiraid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

PR reviews often miss structural risks in code diffs, including SQL safety issues, LLM trust boundary violations, and potentially harmful side effects. This Skill analyzes the current branch's diff against the base branch to surface these risks before merging.

Core Features & Use Cases

  • Diff analysis for SQL safety, LLM trust boundaries, and structural side effects.
  • Applicable to pre-landing PR reviews, code reviews, and diff checks on GitHub and GitLab to catch issues early.
  • Provides actionable remediation guidance and integrates with the gstack review workflow to guide investigators and developers.

Quick Start

Run the review skill on a feature branch to scan its diff against the base branch and surface PR risks.

Frequently Asked Questions about review

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

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

To check a PR diff for SQL safety, run an automated pre-landing review against your base branch. This surfaces SQL injection risks and structural side effects in the code changes, providing actionable remediation guidance before you merge.

What are LLM trust boundary violations in code reviews?▼

LLM trust boundary violations occur when untrusted inputs bypass security checks in LLM workflows. Automated diff analysis identifies these structural risks during pre-landing PR reviews, flagging potentially harmful side effects before integration.

Can I use automated diff analysis for pre-landing reviews on GitHub and GitLab?▼

Yes, automated diff analysis supports pre-landing PR reviews and code checks on both GitHub and GitLab. It scans feature branch diffs against the base branch to surface structural risks early in the merge workflow.

What is the best way to surface structural risks in a feature branch diff?▼

The best way to surface structural risks is running a diff check against the base branch. This process identifies SQL safety issues, LLM trust boundary violations, and side effects, returning actionable findings to guide remediation.

Do I need the gstack workflow to guide remediation for PR risks?▼

No, but using the gstack review workflow provides integration hooks to guide remediation effectively. The diff analysis returns actionable findings that integrate directly into gstack to help investigators and developers fix issues.

When should I not use automated diff checks for code reviews?▼

Automated diff checks should not replace manual reviews for complex business logic. They specifically target SQL safety, LLM trust boundaries, and structural side effects, so use them as a pre-landing safety net rather than a comprehensive code review replacement.

Related Skills

Explore More Software Engineering Skills→
nicholaslocascionicholaslocascio
2

review

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

Community
Advanced
madebynoammadebynoam
2

review

Analyze PR diffs against main for SQL safety and trust boundary risks.

Community
Advanced
AlexandreLabAlexandreLab

gstack-review

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

Community
Advanced
xiaoniuge36xiaoniuge36
6

code-review

Analyze code for standards compliance, bugs, performance issues, and security vulnerabilities.

Community
Advanced