skills.rest
xotong
xotongCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze diffs against the base branch to report code quality and security issues.

2|Updated May 8, 2026
Search Tags:#workflow#diff#pr#code-review#llm-trust
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill review-xotong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/gstack/skills/review
Command: npx skills add https://github.com/xotong/claude-marketplace --skill review-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-heavy PRs often introduce subtle issues: security vulnerabilities, data integrity risks, race conditions, and quality gaps that slip past informal checks. The review skill formalizes a proactive audit of diffs against the base branch, surfacing structural issues, LLM trust boundary concerns, and plan-mode misalignments before merges.

Core Features & Use Cases

  • Detects SQL safety, race conditions, and potential side effects by analyzing diffs and repository state.
  • Flags LLM trust boundary violations, tool misuse, and unstable diffs to prevent unreliable deployments.
  • Generates concrete recommendations, including code-level fixes or mitigations, aligned with a ship-ready workflow.

Quick Start

Install and trigger the PR review by saying “review this PR” to run an automated, safety-focused code review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR code review for SQL safety and race conditions?▼

You can trigger an automated PR review by saying "review this PR". The review then proactively audits the diff against the base branch to surface structural issues, LLM trust boundary concerns, and plan-mode misalignments.

What are LLM trust boundary violations in code diffs?▼

LLM trust boundary violations in code diffs involve tool misuse and unstable deployments caused by over-trusting model outputs. The review skill flags these violations to prevent unreliable merges.

How do I check diffs for security vulnerabilities before a merge?▼

Checking diffs for security vulnerabilities requires analyzing code changes against the base branch to surface data integrity risks, SQL safety concerns, and potential side effects with concrete mitigation recommendations.

Can I get actionable code fixes during a diff review?▼

Yes, you can get actionable code fixes during a diff review. The process generates concrete recommendations and suggested changes to reduce merge risk and align with a ship-ready workflow.

Does automated code review work without external dependencies?▼

Automated code review works without external dependencies by relying on an internal audit of your repository state. It formalizes proactive checks for quality gaps and race conditions directly from the diff analysis.

Related Skills

Explore More Software Engineering Skills→
CoolCoderSuperCoolCoderSuper
4

merge-into-branch

Merge an upstream branch into a Roslyn repository base branch.

Community
Advanced
dogeareddogeared

ship

Automates the end-to-end ship workflow for code changes.

Community
Advanced
tilework-techtilework-tech
149

Finishing a Development Branch

Run tests, formatters, linters, type checks, and submit a PR.

Official
Intermediate
adityaarsharmaadityaarsharma
2

orbit-wp-security

Detect security vulnerabilities in WordPress plugin PHP source code via static analysis.

Community
Advanced