skills.rest
AlejandroFigini
AlejandroFiginiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Analyze PR diffs for SQL safety, LLM trust boundary, and side-effect risks.

Updated Mar 27, 2026
Search Tags:#quality#review#diff#pr#code-review#gstack
One-click install
npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill review-alejandrofigini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/AlejandroFigini/artist-portfolio/tree/main/.agent/skills/review
Command: npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill review-alejandrofigini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the pre-landing PR review process by analyzing diffs to identify SQL safety issues, LLM trust boundary violations, and potential conditional side effects, helping teams ship safer code.

Core Features & Use Cases

  • Analyzes diffs for SQL safety boundaries, ensuring queries are parameterized and free from injection risks.
  • Detects LLM trust boundary violations and potential prompt-injection risks by validating outputs and enforcing safe data flows.
  • Highlights conditional and side-effect risks in changes, enabling proactive risk mitigation before merging.
  • Use Case: A developer asks to review a PR that touches data handling and access control; the skill returns a prioritized list of risks and actionable fixes.

Quick Start

Share the diff or PR link to trigger an automated pre-landing review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for SQL injection risks in a PR diff?▼

Automated code review for SQL injection analyzes PR diffs to verify queries are parameterized and free from injection risks. It surfaces SQL safety boundaries and returns structured findings with actionable recommendations before landing code changes.

What is a pre-landing PR review for LLM trust boundary violations?▼

A pre-landing PR review for LLM trust boundary violations detects prompt-injection risks by validating outputs and enforcing safe data flows. It analyzes diffs to identify potential security boundary compromises and returns traceable references to the code changes.

How do I check a PR diff for conditional side effects before merging?▼

To check a PR diff for conditional side effects, analyze the code changes to highlight potential deployment risks and side-effect conditions. This pre-landing review returns a prioritized list of risks enabling proactive mitigation before merging.

Can I use automated code review for data handling and access control changes?▼

Yes, automated code review applies to pre-landing reviews of code changes touching data handling, security boundaries, or deployment risk. It analyzes the diff to return a prioritized list of risks and actionable fixes across the repository.

What is the best way to review a pull request for deployment risks?▼

The best way to review a pull request for deployment risks is analyzing the diff to surface SQL safety issues, LLM trust boundary violations, and conditional side effects. This approach returns structured findings with actionable recommendations and traceable references.

Related Skills

Explore More Software Engineering Skills→
MFS-codeMFS-code
8

review

Review git diffs for SQL, LLM trust, and concurrency risks.

Community
Advanced
whd4whd4

review

Audit diffs for SQL safety, trust boundary violations, and side effects.

Community
Advanced
s977043s977043
2

code-review

Analyze pull-request diffs to identify security, performance, quality, and test risks.

Community
Basic
mia-cxmia-cx

audit-security

Audits entire codebase for security risks including secrets exposure and misconfigurations.

Official
Advanced