review

Review code diffs for security, performance, correctness, and maintainability issues.

12|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/qdzsh/gsd-revamp --skill review-qdzsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/qdzsh/gsd-revamp/tree/main/src/resources/skills/review
Command: npx skills add https://github.com/qdzsh/gsd-revamp --skill review-qdzsh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changes to identify real issues in security, performance, bugs, and maintainability, providing actionable feedback before merging.

Core Features & Use Cases

  • Parse diffs from staged, unstaged, or committed changes and PRs.
  • Read modified files in full to understand context, tests, and configuration changes.
  • Produce structured findings across security, performance, bug risks, and quality with prioritized recommendations.
  • Integrate with standard code review workflows to accompany diffs with actionable notes.

Quick Start

Run the review workflow on your current changes to generate a structured findings report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code changes to catch security and performance bugs?

To review code changes for security and performance bugs, the system parses staged, unstaged, or committed diffs to surface real issues in correctness and maintainability, providing prioritized and actionable feedback before merging.

What is the best way to analyze pull requests for maintainability and bug risks?

Analyzing pull requests for maintainability and bug risks is best done by reading modified files in full to understand context, tests, and configuration changes, producing structured findings with prioritized recommendations across security, performance, and quality.

Can I use this code review workflow across any programming language?

Yes, you can use this code review workflow across any programming language in a typical git workflow, as it identifies and reviews code changes to surface real issues in security, performance, correctness, and maintainability regardless of language.

How does a structured code review handle tests and configuration changes?

A structured code review handles tests and configuration changes by requiring the reading of full modified files to understand the complete context, ensuring that findings across security, performance, and bug risks are accurate and prioritized.

Does reviewing diffs before merging require reading the full modified files?

Yes, reviewing diffs before merging requires reading full modified files to gather complete context, check for tests and configuration changes, and accurately report findings in a prioritized, actionable format across security and performance dimensions.