review

Analyze code changes for security, performance, bugs, and quality issues.

321|26|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/mkurman/tamux --skill review-mkurman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mkurman/tamux/tree/main/skills/gsd-2/skills/review
Command: npx skills add https://github.com/mkurman/tamux --skill review-mkurman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code changes for security, performance, bugs, and quality across staged changes, unstaged changes, commits, or PR-ready diffs.

Core Features & Use Cases

  • Inspect diffs and surrounding context to identify real issues beyond style nits.
  • Provide structured findings by category (security, performance, bugs, quality) with actionable recommendations.
  • Evaluate test coverage and configuration changes to ensure robust releases.

Quick Start

Run a structured review of the current changes, focusing on security, performance, and maintainability.

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 for security and performance issues?

To review code changes for security and performance issues, you analyze staged changes, unstaged changes, specific commits, or branch diffs. This process evaluates modified files and their context to produce structured findings with severity levels and actionable recommendations.

What is the best way to find bugs in a git diff before merging?

The best way to find bugs in a git diff is to inspect the diff and its surrounding context to identify real issues beyond style nits. This approach evaluates test coverage and configuration changes to ensure robust releases by focusing on security, performance, and maintainability.

Can I use structured code review for specific commits?

Yes, you can use structured code review for specific commits. It applies to staged changes, unstaged changes, commits, or PR-ready diffs, reading each modified file and its context to generate categorized findings suitable for integration into code review workflows.

Does code review work with both staged and unstaged changes?

Code review works with both staged and unstaged changes. It analyzes these variations alongside specific commits and branch diffs to identify security vulnerabilities, performance bottlenecks, bugs, and quality issues, providing structured findings with actionable recommendations.

How do I get actionable recommendations from a code quality review?

To get actionable recommendations from a code quality review, analyze the code changes to produce a defined output schema. This schema categorizes findings by security, performance, bugs, and quality, assigning severity levels to each issue for clear integration into review workflows.