review

Reviews branch diffs against a base branch for SQL safety, race conditions, and structural issues.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill review-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill review-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code review before merging often misses structural issues that tests don't catch, such as SQL injection risks, race conditions, LLM output trust violations, and incomplete enum handling. This Skill automates a pre-landing PR review of your branch's diff against the base branch so these problems surface before code ships. ## Core Features & Use Cases - Two-Pass Diff 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, performance, CI/CD issues) using a structured checklist. - Scope Drift & Plan Completion Audit: Compares the diff against TODOS.md, PR descriptions, and plan files to detect scope creep and missing requirements. - Greptile Comment Triage: Fetches, classifies, and replies to Greptile bot review comments on GitHub PRs with evidence-based responses. - Conditional Design Review: When frontend files change, applies a design checklist covering AI-slop patterns, typography, spacing, and interaction states. - Use Case: Before merging a feature branch, ask for a review and get a report of critical and informational findings, with mechanical fixes auto-applied and ambiguous ones batched into a single question. ## Quick Start Ask the assistant to review this PR or run a pre-landing review of my current branch against main.

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 before merging?

Run the review workflow on your feature branch and it diffs against the detected base branch, then applies a two-pass checklist covering SQL safety, race conditions, and structural issues. Findings are reported as critical or informational with suggested fixes.

What issues does an automated pre-landing code review catch?

It catches string-interpolated SQL, TOCTOU race conditions, unvalidated LLM output written to databases, incomplete enum handling across consumers, dead code, test gaps, and heavy dependency additions. Mechanical issues are auto-fixed while ambiguous ones are asked about.

Does the review work if no pull request exists yet?

Yes. If no PR exists, it falls back to the repo's default branch as the base and uses commit messages and TODOS.md to infer intent. Greptile triage is skipped silently when no PR is available.

How does the review handle Greptile bot comments on GitHub PRs?

It fetches Greptile line-level and top-level comments via the GitHub API, classifies each as valid, already fixed, false positive, or suppressed, and posts evidence-based replies using tiered templates. Per-project history files suppress known false positives.

When does the design review run during code review?

The design review only runs when the diff touches frontend files, detected via a scope script. It checks for AI-slop patterns, typography issues, spacing problems, and missing interaction states, calibrated against DESIGN.md if one exists.