aif-review

Review staged Git changes and pull requests for bugs, security flaws, and performance issues.

2|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/drsapaev/final --skill aif-review-drsapaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/drsapaev/final/tree/main/.codex/skills/aif-review
Command: npx skills add https://github.com/drsapaev/final --skill aif-review-drsapaev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of code review, identifying potential bugs, security vulnerabilities, performance bottlenecks, and deviations from best practices.

Core Features & Use Cases

  • Automated Code Analysis: Analyzes staged code changes or entire pull requests.
  • Comprehensive Checklist: Covers correctness, security, performance, best practices, and testing.
  • Use Case: Before merging a new feature, use this Skill to ensure the code is robust, secure, and adheres to project standards.

Quick Start

Use the aif-review skill to review the code changes you have staged.

Frequently Asked Questions about aif-review

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

FAQPage Schema
How do I automate code review for staged Git changes?

Automating code review for staged Git changes evaluates your diffs against a checklist covering correctness, security, performance, and best practices. It analyzes the staged code to identify bugs and vulnerabilities before you merge.

Can I review an entire GitHub pull request for security and performance?

Reviewing an entire GitHub pull request for security and performance is supported using Git and GitHub CLI. It analyzes the pull request diff to detect security vulnerabilities, performance bottlenecks, and deviations from best practices.

What does an automated code review checklist cover?

A code review checklist covers correctness, security, performance, testing, and best practices. It ensures your staged changes and pull requests are robust, secure, and adhere to established project standards before integration.

Do I need GitHub CLI to analyze code diffs?

GitHub CLI is used to support the analysis of code diffs for pull requests. While Git handles staged changes locally, the GitHub CLI enables fetching and reviewing complete pull request diffs directly from the repository.

When should I run an automated code review before merging?

Run an automated code review before merging a new feature to ensure the code is robust and secure. Analyzing staged changes or pull requests catches potential bugs, security vulnerabilities, and performance issues early in the development workflow.