review

Reviews pull request diffs against main for SQL safety, race conditions, and LLM trust boundary issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review often misses structural issues that tests don't catch, such as SQL injection risks, race conditions, N+1 queries, and unvalidated LLM output written to databases. This Skill automates a pre-landing review of your branch's diff against main using a curated checklist. ## Core Features & Use Cases - Two-Pass Review: Runs a CRITICAL pass (SQL & data safety, race conditions, LLM output trust boundary) followed by an INFORMATIONAL pass (dead code, test gaps, crypto issues, view performance). - Structured Findings: Outputs every issue with file:line citations and one-line fixes, classifying them as blocking or non-blocking. - Interactive Fix Workflow: For each critical issue, asks whether to fix it now, acknowledge it, or dismiss it as a false positive, then applies approved fixes. - Use Case: Before merging a feature branch, run the review to catch a find_or_create_by without a unique index or an LLM-generated email persisted without format validation. ## Quick Start Ask the assistant to run the pre-landing review on the current branch's diff against main and report any critical or informational issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request diff for SQL injection risks?▼

Run the review on your branch, which checks the git diff against main for string interpolation in SQL, missing sanitize_sql_array usage, and update_column calls bypassing validations. Each finding includes the file, line, and a suggested fix.

What code review checklist catches race conditions in Rails?▼

This checklist flags check-then-set patterns that should be atomic WHERE plus update_all, find_or_create_by without unique indexes, and status transitions without atomic updates. It also covers non-constant-time secret comparisons and insecure randomness.

Can the review modify my code automatically?▼

The review is read-only by default and never commits, pushes, or creates PRs. It only edits files when you explicitly choose the fix option for a critical issue through the interactive prompt.

Why does the review say nothing to review on my branch?▼

This happens when you are on the main branch or when git diff against origin/main returns no changes. Switch to a feature branch with committed or uncommitted changes before running the review.

What issues block merging versus informational only?▼

Critical issues blocking merge are SQL and data safety problems, race conditions and concurrency bugs, and LLM output trust boundary violations. Informational findings like dead code, test gaps, and magic numbers are reported but do not block.