review

Review code diffs and project files for bugs, style, security, and architecture issues.

29|2|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/agentty-xyz/agentty --skill review-agentty-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/agentty-xyz/agentty/tree/main/skills/review
Command: npx skills add https://github.com/agentty-xyz/agentty --skill review-agentty-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent, reproducible process for reviewing uncommitted changes, feature-branch diffs, or existing code to surface correctness, security, style, and architectural issues so maintainers and contributors can act quickly and confidently.

Core Features & Use Cases

  • Context-aware diff analysis: Guidance for gathering the right diffs (uncommitted, staged, or branch comparisons) and inspecting project layout and conventions.
  • Comprehensive checks: Recommendations covering style, logic correctness, edge cases, error handling, security vulnerabilities, performance, and test coverage.
  • Actionable reporting: Produces a categorized review report with severity levels and exact, implementable fixes and code snippets where applicable.
  • Use Case: Use to review a pull request or a local feature branch before merging to ensure adherence to project conventions and to identify regressions early.

Quick Start

Review the current branch diff and produce a categorized review report with critical, high, medium, and low issues and exact recommendations.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a code review on staged or uncommitted git diffs?

A code review on uncommitted or staged diffs evaluates changes for bugs, style violations, and security issues. It produces categorized findings with severity labels and actionable, exact recommendations referencing project conventions.

What is the best way to review a feature branch for security vulnerabilities and architectural problems?

Reviewing a feature branch involves context-aware diff analysis that inspects project layout and conventions. It categorizes security vulnerabilities and architectural problems with severity levels and provides actionable, exact recommendations.

Can I use this approach to audit test coverage and logic correctness in an existing codebase?

Yes, you can audit test coverage and logic correctness in an existing codebase. Full-repo audits apply comprehensive checks to surface edge cases, error handling issues, and performance problems, yielding actionable code fixes.

Does the code review process provide actionable fixes or just highlight style guide violations?

The code review process provides actionable fixes, not just style guide violations. It delivers a categorized report with exact, implementable recommendations and code snippets where applicable, referencing project conventions.

When do I need a structured code review report with severity labels for pull requests?

You need a structured code review report with severity labels for pull requests to ensure adherence to project conventions and identify regressions early. This allows maintainers and contributors to act quickly and confidently.