review

Reviews pull request diffs for SQL safety, concurrency, LLM trust boundaries, and test coverage gaps.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill review-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/gstack-review
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill review-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review before merging is often shallow — tests pass but structural issues like SQL injection risks, race conditions, unhandled enum values, and missing test coverage slip through. This Skill performs a systematic pre-landing review of your branch's diff against the base branch, catching the issues that tests don't. ## Core Features & Use Cases - Two-Pass Diff Review: Applies a structured checklist covering SQL & data safety, race conditions, LLM output trust boundaries, enum completeness, dead code, and performance impact. - Scope Drift Detection: Compares the diff against TODOS.md, PR descriptions, and commit messages to flag scope creep or missing requirements. - Test Coverage Diagram: Traces every changed code path and user flow, produces an ASCII coverage map, and generates regression tests for broken behavior. - Design Review: When frontend files change, applies a design checklist calibrated against your repo's DESIGN.md. - Use Case: Before merging a feature branch, ask for a review — the Skill fetches the base branch, analyzes the full diff, triages Greptile bot comments, and presents findings with a fix-first flow. ## Quick Start Ask the AI to review my current branch's changes against the base branch before I merge this PR.

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. It detects the base branch via the GitHub CLI, fetches the latest state, and applies a structured checklist covering SQL safety, concurrency, and LLM trust boundaries across the full diff.

What issues does automated pre-landing code review catch?

It catches structural problems tests miss: SQL injection risks, race conditions, unvalidated LLM outputs, incomplete enum handling, conditional side effects, dead code, and test coverage gaps. Findings are split into critical and informational passes.

Does this code review work without an existing pull request?

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 comment triage is skipped silently when no PR is available.

How does the review detect missing test coverage?

It traces every changed code path and user flow, builds an ASCII coverage diagram rating existing tests, and flags gaps. Regressions get tests written immediately; other gaps follow a fix-first flow with auto-fix or ask classification.

Can the review check frontend design changes?

Yes, when the diff touches frontend files it runs a conditional design review calibrated against your repo's DESIGN.md. Mechanical CSS fixes are auto-fixed, while design judgment items are presented for confirmation.