review

Reviews pull request diffs for SQL safety, race conditions, and LLM trust boundary violations.

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill review-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/kitfunso/claude-config/tree/main/skills/review
Command: npx skills add https://github.com/kitfunso/claude-config --skill review-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Catching structural bugs like SQL injection, race conditions, and unvalidated LLM output before code merges is hard to do consistently by eye, and generic review comments often create noise instead of signal. ## Core Features & Use Cases - Two-pass pre-landing review: Runs a critical pass (SQL & data safety, race conditions, LLM output trust boundary, enum completeness) followed by an informational pass (dead code, test gaps, crypto entropy, type coercion, view performance) against a git diff or a pasted diff. - Fix-first triage: Automatically applies mechanical fixes (dead code, N+1 eager loading, magic numbers) while batching judgment calls (security, design decisions, large fixes) into a single structured user question. - Greptile comment triage: Fetches, classifies, and replies to Greptile bot review comments on GitHub PRs with evidence-backed templates and per-project false-positive suppression history. - Use Case: Before merging a feature branch, ask for a pre-landing review; the skill checks git diff origin/main, flags a string-interpolated SQL query as a blocking P0 finding, auto-fixes a stale comment, and replies to two Greptile comments on the PR. ## Quick Start Ask the AI to review this PR or check my diff before it merges, optionally pasting a diff directly into the chat.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff for SQL injection before merging?▼

Run a pre-landing review on the output of git diff origin/main or paste the diff into chat. The review flags string interpolation in SQL queries as a critical finding with file and line references, and recommends parameterized queries instead.

What does a pre-landing code review check for?▼

It runs two passes: a critical pass covering SQL and data safety, race conditions, LLM output trust boundaries, and enum completeness, then an informational pass covering dead code, test gaps, crypto entropy, time windows, type coercion, and view performance.

Can it review a diff pasted into chat without a branch?▼

Yes. The skill accepts either a git diff against the base branch or a diff pasted directly into the chat, applying the same checklist categories and severity classification to both inputs.

Does the review auto-fix issues or just report them?▼

It uses a fix-first heuristic: mechanical fixes like dead code removal, N+1 eager loading, and magic number extraction are applied automatically, while security issues, race conditions, and large fixes are batched into a single question for the user.

How does it handle Greptile bot comments on GitHub PRs?▼

It fetches Greptile line-level and top-level comments via the gh API, classifies each as valid, already fixed, false positive, or suppressed based on per-project history, and posts evidence-backed replies using tiered templates.

When does the design review checklist run?▼

The design checklist only runs when the diff touches frontend files, detected via a diff-scope helper. It flags AI-slop patterns, typography issues, missing focus states, and violations of the project's DESIGN.md, and skips silently otherwise.