review

Analyze code diffs against the base branch to identify critical issues.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill review-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-review
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill review-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of merging code with undetected critical issues such as SQL injection vulnerabilities, LLM trust boundary violations, conditional side effects, and structural flaws that can cause production outages or security breaches.

Core Features & Use Cases

  • Diff Analysis: Automatically analyzes code changes against the base branch to identify potential issues.
  • Safety Checks: Flags SQL safety risks, LLM trust boundary violations, and unintended conditional side effects.
  • Proactive Suggestions: Automatically recommends review when you are about to merge or land code changes.
  • Use Case: Engineering teams can use this Skill to standardize pre-landing code review checks, reducing the chance of shipping buggy or insecure code.

Quick Start

Ask the AI to run the review skill on your current PR diff to check for SQL safety, LLM trust boundary violations, and structural issues before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform pre-landing code review to catch SQL injection vulnerabilities in a PR?

Pre-landing code review analyzes pull request diffs against the base branch to detect SQL injection vulnerabilities before merge. It flags SQL safety risks by inspecting code changes, ensuring that insecure query construction does not reach production environments.

What is an LLM trust boundary violation and how does pre-landing review detect it?

An LLM trust boundary violation occurs when untrusted input improperly influences model execution. Pre-landing PR review detects this by analyzing code diffs to identify structural flaws where user inputs bypass security compliance checks before interacting with LLM components.

How do I check for conditional side effects and structural flaws before merging code?

To check for conditional side effects before merging, analyze your code diffs against the base branch. Pre-landing review validates merge safety by automatically detecting unintended conditional side effects and structural code quality issues within the proposed changes.

Does pre-landing PR review work for security compliance checks in engineering workflows?

Yes, pre-landing PR review works for security compliance checks in engineering workflows. It standardizes pre-deployment quality assurance by analyzing code changes to enforce merge validation, flagging SQL safety risks and LLM trust boundary violations before integration.

Can I automate merge validation for structural code quality assessment?

Yes, you can automate merge validation for structural code quality assessment. By applying pre-landing review to your PR diff, the system proactively recommends safety checks and evaluates structural flaws, reducing the chance of shipping insecure code.