review

Parse code diffs and surrounding context to surface security, performance, bug, and maintainability issues.

1.0k|92|Updated May 22, 2026
One-click install
npx skills add https://github.com/open-gsd/gsd-pi --skill review-open-gsd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/open-gsd/gsd-pi/tree/main/src/resources/skills/review
Command: npx skills add https://github.com/open-gsd/gsd-pi --skill review-open-gsd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes are prone to hidden issues that slip through reviews. This skill provides a structured, repeatable way to analyze diffs and surrounding context to surface security flaws, performance bottlenecks, bugs, and maintainability risks before merges.

Core Features & Use Cases

  • Parse diffs and surrounding context to identify issues across security, performance, bugs, and maintainability.
  • Return structured findings with severity levels and concrete remediation suggestions.
  • Support multiple review scopes (staged changes, unstaged changes, specific commits, or PR ranges) and flag potential test gaps and risky changes.
  • Use case: review a PR diff to quickly surface critical issues and align on fixes before merge.

Quick Start

Describe the changes to review (for example, '/review pr' or '/review <commit>') and the tool will fetch diffs and generate findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for a pull request diff?

Automate code review by parsing a PR diff and surrounding context to surface security, performance, bug, and maintainability issues. The tool fetches modified files and generates structured findings with severity levels and remediation suggestions.

What issues can a structured code review catch before merge?

A structured code review catches hidden security flaws, performance bottlenecks, bug risks, and maintainability issues. It analyzes staged or unstaged changes to flag potential test gaps and risky modifications before code merges.

Can I review specific git commits instead of a full pull request?

Yes, you can review specific git commits. The tool supports multiple review scopes including staged changes, unstaged changes, individual commits, and PR ranges to analyze modified files and surrounding code context.

How does code review automation handle severity and remediation?

Code review automation handles severity by assigning levels to each finding and providing concrete remediation suggestions. It produces a review-ready summary aligning developers on necessary fixes before merging.

What's the best way to surface security risks in staged changes?

The best way to surface security risks in staged changes is to parse the diff and surrounding context. This identifies vulnerabilities and returns structured findings with severity levels and remediation suggestions.

Does automated code review flag missing tests in modified files?

Yes, automated code review flags potential test gaps in modified files. It analyzes the diff and surrounding context to identify risky changes and produces a review-ready summary highlighting these gaps.