review

Review code changes for security, correctness, and quality issues.

19|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dirien/yet-another-agent-harness --skill review-dirien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/review
Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill review-dirien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code changes to surface security vulnerabilities, correctness bugs, quality regressions, performance problems, and missing or inadequate tests so maintainers can make informed merge decisions quickly.

Core Features & Use Cases

  • Focused Diffs and PRs: Analyze PRs or local diffs and read each changed file for full context before making judgments.
  • Comprehensive checks: Look for security issues (injection, XSS, hardcoded secrets), correctness bugs (edge cases, race conditions), quality concerns (naming, duplication), performance hotspots, and test coverage gaps.
  • Actionable reports: Produce findings grouped by severity (CRITICAL, WARNING, SUGGESTION) with file:line references and suggested fixes.
  • Workflow integration: Use during code review, CI triage, or pre-merge checks to prioritize urgent fixes and guide maintainers.

Quick Start

Run the review skill on a pull request or local diff to produce a grouped CRITICAL, WARNING, and SUGGESTION report with file:line references and suggested fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check my pull request for security vulnerabilities and correctness bugs?

To check a pull request for security vulnerabilities and correctness bugs, analyze the code changes to surface injection flaws, race conditions, and edge cases. This process categorizes findings by severity and provides file:line-specific fixes to guide maintainers.

What is the best way to review local git diffs before merging?

Reviewing local git diffs before merging involves reading staged and unstaged changes for full context. This identifies quality regressions, performance hotspots, and missing tests, producing actionable reports with CRITICAL, WARNING, and SUGGESTION classifications.

Can I find hardcoded secrets and XSS issues during code review?

Yes, you can find hardcoded secrets and XSS issues during code review by analyzing the changed files. The review process specifically targets security issues like injection vulnerabilities and hardcoded secrets, recommending precise fixes to resolve them.

Does this code review process assess test coverage gaps and performance issues?

This code review process does assess test coverage gaps and performance issues. It evaluates the diff comprehensively to find missing or inadequate tests and performance hotspots, ensuring maintainers make informed merge decisions quickly.

How do I generate a severity-ranked report for CI triage?

To generate a severity-ranked report for CI triage, run a review on your pull request or local diff. It produces grouped CRITICAL, WARNING, and SUGGESTION findings with file:line references and suggested fixes to prioritize urgent patches.

When do I need to run a pre-merge code quality check?

You need to run a pre-merge code quality check when preparing to merge branches or triage CI pipelines. It evaluates diffs for style issues, duplication, and correctness bugs, providing actionable feedback before code integration.