review

Review git diffs for correctness, security, performance, and pattern adherence.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill review-lalulali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/review
Command: npx skills add https://github.com/lalulali/vespyr --skill review-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review recent code changes without running the full development workflow, so you can quickly catch defects, security issues, and pattern drift before code lands.

Core Features & Use Cases

  • Correctness Checks: Looks for logic errors, edge cases, null handling problems, and missing test coverage.
  • Security and Performance Review: Flags input validation gaps, unsafe auth flows, data exposure risks, N+1 queries, and unnecessary allocations.
  • Pattern Compliance: Compares changed files against project conventions stored in patterns-and-conventions.md.
  • Use Case: Use it when you want a focused review of a PR or recent commit and need actionable findings with file and line references.

Quick Start

Review my recent changes and return blocking, non-blocking, and nit findings with file:line references.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review recent git diff changes for security and performance issues before merging?

To review recent git diff changes, you can analyze pull requests or standalone change sets to flag security gaps, N+1 queries, and logic errors. This provides severity-ranked findings with specific file and line references without executing the full development cycle.

What is the best way to check if my code changes adhere to existing project conventions and patterns?

Checking project pattern compliance involves comparing changed files against conventions stored in a patterns-and-conventions.md file. This identifies pattern drift and ensures new code follows established architectural rules before landing in the main branch.

Can I get a code review on a standalone change set without running the full development workflow?

Yes, you can review standalone change sets without running the full development workflow. This targeted approach inspects git diffs to triage correctness, security, and performance issues, returning actionable blocking, non-blocking, and nit findings.

How do I catch logic errors and missing test coverage in a recent commit?

To catch logic errors and missing test coverage in a recent commit, perform a focused correctness check on the changes. This identifies edge cases, null handling problems, and gaps in test coverage with direct file:line references.

Does this code review process flag input validation gaps and unsafe authentication flows?

Yes, the code review process explicitly flags input validation gaps, unsafe authentication flows, and data exposure risks. It inspects code changes to catch these security vulnerabilities alongside performance issues like unnecessary allocations.

How should I format my request to get severity-ranked findings with file and line references?

To get severity-ranked findings with file and line references, request a focused review of your recent changes. The output categorizes findings into blocking, non-blocking, and nit issues, each annotated with specific file and line locations for easy triage.