code-review

Automate pull request code reviews for security, performance, and quality issues.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/reynalivan/EMMM2 --skill code-review-reynalivan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/reynalivan/EMMM2/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/reynalivan/EMMM2 --skill code-review-reynalivan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automated code review helps teams catch quality, security, and performance issues in PRs and code changes, reducing risk and speeding up audits.

Core Features & Use Cases

  • Standardized audit process across backend Rust and frontend React codebases.
  • Security-first checks for secrets, unsafe patterns, and risky API usage based on the provided checklists.
  • Performance and quality evaluations aligned with the performance_checklist.md and quality_checklist.md.
  • Use Case: When reviewing a PR, generate a structured report highlighting critical and warning items with actionable remediation steps.

Quick Start

Review the provided PR or code changes and generate a structured audit focusing on security, performance, and quality.

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 pull requests to catch security and performance issues?

Automated code review for pull requests identifies security, performance, and quality issues by enforcing a standardized audit workflow. It analyzes PR changes and generates a structured report highlighting critical items with actionable remediation steps.

Can I use automated code review for Rust backend and React frontend projects?

Yes, automated code review supports standardized audits across Rust backend and React frontend projects. It evaluates code changes using security-first, performance-second, and quality-third checks based on provided checklists.

What is the best way to audit code changes for unsafe patterns and risky API usage?

Auditing code changes for unsafe patterns relies on a security-first checklist that detects secrets, unsafe patterns, and risky API usage. This standardized process prioritizes security checks before evaluating performance and code quality.

How do I generate a structured report from a pull request code audit?

To generate a structured report from a pull request code audit, review the PR changes and apply the security, performance, and quality checklists. The output highlights critical and warning items with actionable remediation steps.

Does static analysis code review enforce a specific checklist order for quality checks?

Yes, static analysis code review enforces a strict checklist order: security checks first, performance evaluations second, and quality assessments third. This ensures vulnerabilities are caught before optimizing execution speed or code structure.

When do I need a standardized code audit workflow instead of manual PR reviews?

A standardized code audit workflow is needed when reviewing PRs across multiple codebases like Rust and React to reduce risk and speed up audits. It replaces manual reviews by consistently catching secrets, unsafe patterns, and performance bottlenecks.