code-review

Identify security, quality, and maintainability issues in pull requests.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/eszxcvfd/ANIZAKI --skill code-review-eszxcvfd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/eszxcvfd/ANIZAKI/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/eszxcvfd/ANIZAKI --skill code-review-eszxcvfd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes thorough code reviews to identify security, quality, and maintainability issues with actionable guidance.

Core Features & Use Cases

  • Identify changes by running git diff to surface modified files and determine the scope of the review.
  • Review categories cover Security, Code Quality, Performance, Best Practices, and Maintainability with structured checks and guidance.
  • Output provides a Code Review Report including files reviewed, issues by severity, specific file:line locations, and concrete fix recommendations.

Quick Start

Run a full code review on the current pull request and review the generated report for actionable fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for security and maintainability issues?

Automate code review by running git diff to surface modified files, then checking security, quality, and maintainability to generate a prioritized report with concrete file:line recommendations.

How does code review identify issues in a pull request?

Code review identifies issues by analyzing changed files or the full codebase, categorizing findings by severity, and providing specific file:line locations alongside concrete fix suggestions.

What is the best way to generate actionable code review reports?

Generate actionable code review reports by analyzing the pull request scope and outputting a structured report containing reviewed files, issues by severity, fix recommendations, and an explicit approval or request-for-changes stance.

Can I review code quality and performance on modified files only?

Yes, you can review code quality and performance on modified files only by running git diff to determine the review scope, or you can operate on the full codebase as needed.

Does automated code review provide an approval or request-for-changes stance?

Yes, automated code review provides an explicit approval or request-for-changes stance in the final report, delegating the thorough checks to a code-review agent while prioritizing identified issues.

When do I need a structured code review report for my pull request?

You need a structured code review report when you want to standardize quality checks across security, performance, and best practices, receiving prioritized fix suggestions with specific file:line locations.