review

Analyze diffs, PRs, branches, or files to generate severity-organized code review reports.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/sqfzy/my_configs --skill review-sqfzy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sqfzy/my_configs/tree/main/claude/skills/review
Command: npx skills add https://github.com/sqfzy/my_configs --skill review-sqfzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs, PRs, branches, or specific files to generate structured, actionable code review feedback that helps teams pinpoint defects, architectural concerns, and debt without modifying code by default.

Core Features & Use Cases

  • Review diffs and commits to surface correctness, security, and design issues.
  • Perform full-project audits to identify architectural concerns, patterns, and debt across the codebase.
  • Generate a ready-to-share report organized by severity, focused on actionable recommendations and next steps.

Quick Start

Provide a diff, PR, branch, or file set to produce a structured review report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I generate actionable code review feedback on a pull request?

You can generate actionable code review feedback by providing a pull request, diff, or branch for analysis. The system produces a structured, severity-organized report highlighting correctness, security, and design issues.

Can I perform a full-project audit to identify architectural concerns and code debt?

Yes, you can perform a full-project audit to identify architectural concerns, patterns, and code debt across the entire codebase. This mode surfaces broader structural issues beyond individual diffs.

Does the code review process automatically modify my source files?

No, the code review process operates in read-only mode by default and does not modify your source files. It only applies changes when explicitly requested using commands like /fix or /refactor.

What is the best way to organize code review findings for team sharing?

The best way to organize code review findings for sharing is through a ready-to-share, severity-organized report. This report focuses on actionable recommendations and next steps for the team.

How do I automatically fix issues found during a diff analysis?

To automatically fix issues found during a diff analysis, you must explicitly request changes using commands like /fix or /refactor. Without these explicit commands, the review remains read-only.