code-review

Identify security, performance, and correctness issues in code changes.

Updated Aug 23, 2026

Search Tags:#performance #security #maintainability #ci-cd #code-review #correctness #pull-request

Ready to run

npx skills add https://github.com/PoyoPoak/FastAPI-App-Template --skill code-review-poyopoak

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/PoyoPoak/FastAPI-App-Template/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/PoyoPoak/FastAPI-App-Template --skill code-review-poyopoak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes for security, performance, and correctness to prevent faulty deployments and security risks.

Core Features & Use Cases

Structured review dimensions covering Security, Performance, Correctness, and Maintainability.
PR-based workflow that surfaces issues for diffs, merges, and file changes across repositories.
Actionable, markdown-formatted output including a summary, critical issues, suggestions, and a verdict.

Quick Start

Submit a PR URL or file path to generate a structured review report.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review code changes for security and performance issues before merge?▼

To review code changes for security and performance issues, submit a pull request URL or file path. This generates a markdown report with a summary, critical issues, suggestions, and a final verdict.

What is the best way to automate spotting N+1 queries and injections in a pull request?▼

Automated code review identifies N+1 queries and injections in diffs by applying a structured checklist across security, performance, and correctness dimensions.

Can I use this code review process for file changes across any repository?▼

Yes, you can use this code review process for file changes across any repository. It is applicable to diffs, merges, and pull requests without requiring specific repository dependencies.

Does the code review report include a verdict on whether to merge the code?▼

Yes, the code review report includes a verdict on whether to merge the code. The markdown output contains a summary, critical issues, suggestions, and a final verdict.

How does the code review process handle missing error handling and edge cases?▼

The code review process handles missing error handling and edge cases by evaluating correctness. It surfaces these risks in the final markdown report to prevent faulty deployments.

When do I need a structured checklist for reviewing pull requests?▼

You need a structured checklist for reviewing pull requests when you want to prevent faulty deployments and security risks. It ensures coverage of maintainability, performance, and correctness issues.