skills.rest
Yaugourt
YaugourtCOMMUNITY
Explore all skills by this author →
𝕏@YaugourtGitHub

review

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

2|2|Updated Dec 1, 2024
Search Tags:#review#code-review#pull-request#diff-analysis#llm-trust
One-click install
npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill review-yaugourt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill review-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-based PR review helps teams catch structural issues: SQL safety lapses, LLM trust boundary violations, and risky side effects, before merging.

Core Features & Use Cases

  • Analyzes diffs against the base branch to surface SQL safety issues, trust boundary violations, and conditional side effects.
  • Provides proactive guidance for pre-landing reviews and when checking diffs in PRs.
  • Delivers actionable recommendations and highlights exact files/lines to inspect.

Quick Start

Provide a PR diff or link and I will return a structured review with identified issues and recommended fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request diff for SQL safety and LLM trust boundary issues?▼

To review a pull request diff for SQL safety and LLM trust boundary issues, provide the PR diff or link. The tool analyzes the diff against the base branch to identify structural issues and provides actionable recommendations with exact file and line references.

What is diff analysis in pre-landing code reviews?▼

Diff analysis in pre-landing code reviews is the process of examining changes against a base branch to surface structural problems. It identifies SQL safety lapses, LLM trust boundary violations, and risky conditional side effects before merging code.

Can I use automated code review to catch conditional side effects before merge?▼

Yes, you can use automated code review to catch conditional side effects before merge. By analyzing pull request diffs against the base branch, the review process highlights risky side effects and delivers actionable recommendations to inspect exact files and lines.

What's the best way to identify LLM trust boundary violations in a code diff?▼

The best way to identify LLM trust boundary violations in a code diff is to apply diff analysis against the base branch. This surfaces trust boundary violations alongside SQL safety issues, providing proactive guidance for pre-landing reviews with exact file and line references.

Do I need to provide a full repository to get a structured PR review?▼

No, you do not need to provide a full repository to get a structured PR review. You only need to provide a PR diff or link, and the tool will return a structured review with identified issues and recommended fixes referencing exact files and lines.

When do I need to check diffs for SQL safety issues?▼

You need to check diffs for SQL safety issues during pre-landing PR reviews before merging code. Analyzing the diff against the base branch surfaces SQL safety lapses and other structural issues, allowing you to apply fixes proactively.

Related Skills

Explore More Software Engineering Skills→
SeaLion-hubSeaLion-hub

review

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

Community
Advanced
catu-aicatu-ai
12

harness-land

Merge an approved pull request after confirming an archived harness plan.

Official
Intermediate
rsmdtrsmdt
381

specification-compliance

Validate implementations against documented specifications with structured compliance reporting.

Community
Advanced
voidrotvoidrot

sast-configuration

Configure SAST tools like Semgrep, CodeQL, and SonarQube for CI/CD pipelines.

Community
Intermediate