review

Review code changes for security, performance, bug, and test coverage issues.

1|Updated Jul 13, 2026

Search Tags:#testing #diff analysis #code review #performance #security #bugs

Ready to run

npx skills add https://github.com/vh2224/forge-executor --skill review-vh2224

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/review
Command: npx skills add https://github.com/vh2224/forge-executor --skill review-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect code changes before they ship, so you can catch security flaws, bug risks, performance regressions, and missing tests early.

Core Features & Use Cases

Diff Review: Analyze staged changes, unstaged work, specific commits, or pull-request-ready diffs.
Context-Aware Analysis: Read surrounding source files and related tests to understand intent and avoid false positives.
Risk-Focused Feedback: Surface concrete issues in security, performance, correctness, code quality, and test coverage.
Use Case: A developer asks you to review a branch before opening a PR, and you return a structured list of actionable findings with severity and file references.

Quick Start

Ask me to review the current changes in your repository and report any real issues with clear severity, file references, and fix suggestions.

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 before opening a pull request?▼

To review code changes before a pull request, you analyze staged diffs, unstaged work, or commits to identify security flaws, bug risks, and performance regressions. Reading surrounding source files provides context to produce structured, severity-ranked findings.

How does context-aware code review find real bugs in a diff?▼

Context-aware code review finds real bugs by reading the full changed files and surrounding code rather than isolated diffs. This approach understands intent, avoids false positives, and surfaces concrete issues in correctness, security, and performance.

Can I analyze specific commits for security and performance issues?▼

Yes, you can analyze specific commits for security and performance issues. The review process applies to staged changes, unstaged work, individual commits, and pull-request-ready branches to detect concrete risks and missing test coverage.

What is the best way to check test coverage in staged changes?▼

The best way to check test coverage in staged changes is to review the diff alongside related test files. This identifies missing tests and ensures code quality, correctness, and security before merging the branch.

Does automated diff analysis work on unstaged work in a local repository?▼

Yes, automated diff analysis works on unstaged work in a local repository. It inspects unstaged changes to catch bug risks and code quality issues, reading surrounding context to generate actionable findings with file references.

When should I not rely on a diff review for finding code issues?▼

You should not rely solely on diff review when surrounding context files are inaccessible, as the analysis requires reading full changed files to understand intent and avoid false positives in security, performance, and correctness findings.