review

Assess Git code changes for quality, security, and performance issues.

1|Updated Aug 18, 2025

Search Tags:#git #security #reporting #quality #diff #code-review

Ready to run

npx skills add https://github.com/abhinav8888/dot-files --skill review-abhinav8888

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/abhinav8888/dot-files/tree/main/claude/.claude/skills/review
Command: npx skills add https://github.com/abhinav8888/dot-files --skill review-abhinav8888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently identify quality, security, and performance issues in code changes, reducing time spent on manual reviews and lowering risk in deployments.

Core Features & Use Cases

Review all staged and unstaged changes and, if needed, recent commits to capture the full scope of a diff
Group findings by severity: Critical > Warning > Info
Include the file path and line number for each finding and propose actionable fixes for high-severity items
Generate a concise, actionable report suitable for team reviews and pull requests

Quick Start

Review the current Git workspace to generate a code-review report.

Frequently Asked Questions about review

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

FAQPage Schema

How do I review git diff output for security and code quality issues?▼

Code review of git diff output identifies quality, security, and performance issues by analyzing staged, unstaged, and recent commits, generating structured findings grouped by severity with actionable fixes and file line numbers.

Can I use automated code review to analyze recent git commits?▼

Automated code review can analyze recent git commits alongside staged and unstaged changes to capture the full scope of a diff, producing a concise report suitable for team reviews and pull requests.

What is the best way to generate a code review report for a pull request?▼

The best way to generate a code review report is by assessing all git workspace changes, grouping findings by severity levels like Critical and Warning, and proposing actionable fixes for high-severity items with exact file paths.

How does a code review tool categorize security and performance findings?▼

A code review tool categorizes security and performance findings by grouping them into severity levels: Critical, Warning, and Info, ensuring high-severity vulnerabilities are addressed first with actionable recommendations.

Do I need to stage my changes before running a git code review?▼

You do not need to stage changes before a git code review because the process applies to staged, unstaged, and recent commits, allowing you to review all workspace modifications or a subset as needed.