review

Analyze code diffs for SQL injection, race conditions, and design inconsistencies.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/JacksonZx535/kingsight --skill review-jacksonzx535
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/JacksonZx535/kingsight/tree/main/review
Command: npx skills add https://github.com/JacksonZx535/kingsight --skill review-jacksonzx535

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Edit, Write, Grep, Glob, AskUserQuestion, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the pre-landing PR review process, identifying potential issues in code, design, and documentation before they reach production.

Core Features & Use Cases

  • Automated Code Review: Analyzes diffs for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Design Review: Checks frontend files against design guidelines and flags inconsistencies.
  • Documentation Staleness Check: Ensures documentation remains up-to-date with code changes.
  • Greptile Integration: Incorporates feedback from automated code review tools like Greptile.

Quick Start

Run the 'review' skill to analyze the current branch's diff 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 does automated pre-landing PR analysis detect SQL injection and race conditions?

Automated pre-landing PR analysis scans code diffs to detect SQL injection and race conditions by evaluating structural changes against safety boundaries. It identifies conditional side effects and LLM trust violations before code merges.

How do I check if documentation is stale compared to my current code changes?

To check for documentation staleness, analyze your code diff to ensure documentation remains up-to-date with code changes. This automated review flags inconsistencies between modified files and existing docs.

Can I integrate automated code review tools like Greptile with my PR workflow?

You can integrate automated code review tools like Greptile with your PR workflow to incorporate automated feedback. This combines diff analysis with external tool insights for design and code review.

What is the best way to review frontend design inconsistencies before a PR lands?

The best way to review frontend design inconsistencies is checking frontend files against design guidelines during pre-landing analysis. This flags design inconsistencies automatically before production deployment.

Do I need Bash and Grep to automate PR analysis for potential code issues?

Automating PR analysis for potential code issues requires Bash, Read, Edit, Write, Grep, and Glob tools to function. These dependencies enable the skill to parse diffs and evaluate structural changes.