review

Review pull request diffs for SQL safety and LLM boundary violations.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/miko06/MedicineSimulator --skill review-miko06
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/miko06/MedicineSimulator/tree/main/.opencode/skills/gstack-review
Command: npx skills add https://github.com/miko06/MedicineSimulator --skill review-miko06

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of reviewing pull requests by automatically checking for SQL safety, LLM boundary violations, and other structural issues.

Core Features & Use Cases

  • Automated PR Review: Analyzes diffs against the base branch to detect potential issues.
  • SQL Safety Checks: Ensures that SQL queries in the code do not contain unsafe conditions.
  • LLM Boundary Violations: Checks for boundary violations related to the use of large language models.
  • Use Case: When you are asked to "review this PR", "code review", "pre-landing review", or "check my diff", use this Skill to automate the review process.

Quick Start

Run the 'review' skill to analyze the pull request against the base branch for potential issues.

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 safety and LLM boundary violations?

You can automate code review by running this Skill to analyze pull request diffs against the base branch. It detects unsafe SQL conditions and LLM boundary violations within your code changes automatically.

What is an LLM boundary violation in a pull request?

An LLM boundary violation occurs when code changes improperly handle large language model constraints. This automated review checks your pull request diff to detect potential structural issues and boundary violations related to the use of large language models.

Does this automated pull request review tool check for unsafe SQL conditions?

Yes, this automated pull request review tool performs SQL safety checks to ensure that SQL queries in your code do not contain unsafe conditions. It analyzes your diffs against the base branch to detect these potential SQL issues.

What do I need to run pre-landing code reviews on my diff?

To run pre-landing code reviews on your diff, you need a software engineering workflow environment with Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, and WebSearch tools. The base branch is used for diff comparison.

When should I use an automated code review skill for my pull requests?

You should use an automated code review skill when you are asked to review a PR, perform a pre-landing review, or check a diff. It simplifies the process by automatically checking for SQL safety and LLM boundary violations.

What are the limitations of using automated PR review for LLM boundary violations?

The limitations of automated PR review include its specific focus on SQL safety, LLM boundary violations, and structural issues. It requires specific tools like Bash, Read, Edit, and WebSearch, and operates by analyzing diffs against the base branch.