skills.rest
Vinnni002
Vinnni002COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze pull request diffs against the main branch for SQL safety and LLM trust boundary issues.

Updated Aug 23, 2026
Search Tags:#code quality#automation#code review#pull request#llm#sql safety
One-click install
npx skills add https://github.com/Vinnni002/Sikshak --skill review-vinnni002
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Vinnni002/Sikshak/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/Vinnni002/Sikshak --skill review-vinnni002

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the pre-landing review of code changes in a Pull Request, identifying structural issues, SQL safety violations, and LLM trust boundary problems that automated tests might miss.

Core Features & Use Cases

  • Automated Code Analysis: Analyzes diffs against the main branch for critical issues.
  • Checklist-Driven Review: Follows a defined checklist for comprehensive checks.
  • Use Case: Before merging a new feature, run this Skill to ensure the code is safe, adheres to best practices, and doesn't introduce subtle bugs related to data handling or LLM interactions.

Quick Start

Run the review skill to analyze the current branch's diff against main for structural issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pull request code review before merging?▼

Automated pull request code review is performed by analyzing branch diffs against the main branch to identify structural issues, SQL safety violations, and LLM trust boundary problems before merging.

What is an LLM trust boundary violation in a code review?▼

An LLM trust boundary violation occurs when code improperly handles data interactions with large language models. The review process identifies these issues by analyzing diffs to ensure safe data handling and prevent subtle bugs.

How do I check SQL safety in a pull request diff?▼

You can check SQL safety in a pull request diff by running an automated review that analyzes the changes against the main branch to detect potential database safety violations and conditional side effects.

Does this automated code review integrate with Greptile for comment analysis?▼

Yes, the automated code review integrates with Greptile to provide additional comment triage and analysis, helping to evaluate structural issues found within the pull request diffs.

What structural issues can a pre-landing code review identify?▼

A pre-landing code review identifies structural issues such as SQL safety violations, LLM trust boundary problems, and conditional side effects by following a defined checklist during the diff analysis.

Can I use this code review to catch bugs that automated tests miss?▼

Yes, you can use this checklist-driven code review to catch subtle bugs related to data handling or LLM interactions that automated tests might miss before merging a new feature.

Related Skills

Explore More Software Engineering Skills→
coco-researchcoco-research
264

gsd-pr-branch

Create a clean pull request branch by filtering out planning commits.

Community
Intermediate
DevelonautDevelonaut
3

merge-pr

Verify CI checks, detect conflicts, and squash-merge approved pull requests.

Community
Advanced
roach88roach88
2

await-greptile

Automate pull request reviews by monitoring Greptile, fixing issues, and merging approved PRs.

Community
Advanced
23000311472300031147

review

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

Community
Advanced