review

Analyze pull request diffs against the main branch for critical issues.

5|2|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/lmanchu/iris-system --skill review-lmanchu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lmanchu/iris-system/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/lmanchu/iris-system --skill review-lmanchu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the critical pre-landing review of code changes in a Pull Request, identifying potential structural issues, safety concerns, and LLM-related risks before they are merged.

Core Features & Use Cases

  • Automated Code Analysis: Scans code diffs against the main branch for common pitfalls.
  • Safety & Security Checks: Identifies SQL injection risks, race conditions, and LLM trust boundary violations.
  • Use Case: Before merging a new feature, run /review to get an automated check for critical bugs, security vulnerabilities, and LLM prompt issues, ensuring code quality and stability.

Quick Start

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

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pre-landing code review on a pull request?

Automated pre-landing code review analyzes pull request diffs against the main branch to identify critical structural issues and safety concerns before merging. It scans code changes for common pitfalls using Git, Bash, and Read tools.

What security checks can automated code review perform on git diffs?

Automated code review on git diffs detects security vulnerabilities including SQL injection risks, race conditions, and conditional side effects. It performs safety checks by analyzing the differences between the current branch and the main branch.

Does automated pull request review detect LLM trust boundary violations?

Automated pull request review detects LLM trust boundary breaches by analyzing code diffs against the main branch. It identifies specific LLM-related risks and prompt issues to ensure application stability and security before code changes are merged.

What do I need to run an automated code analysis on my current branch?

Running automated code analysis on your current branch requires Git, Bash, and Read tools to fetch diffs and access checklists. The review skill compares your branch's diff against the main branch to find critical bugs.

When should I run an automated code review before merging a new feature?

You should run automated code review before merging a new feature to get an automated check for critical bugs, security vulnerabilities, and LLM prompt issues. This ensures code quality and stability by identifying structural problems early in the development cycle.