aif-review

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

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Skro11X/all_vibe_code_test --skill aif-review-skro11x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/Skro11X/all_vibe_code_test/tree/main/.claude/skills/aif-review
Command: npx skills add https://github.com/Skro11X/all_vibe_code_test --skill aif-review-skro11x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and 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, ensuring higher code quality.

Core Features & Use Cases

  • Automated Code Analysis: Analyzes staged changes or entire pull requests.
  • Comprehensive Checklist: Covers correctness, security, performance, best practices, and testing.
  • Contextual Awareness: Integrates with project-specific rules and architecture documents.
  • Use Case: Before merging a new feature, use this Skill to perform a thorough review of the code changes, catching potential issues early in the development cycle.

Quick Start

Use the aif-review skill to review the code changes in the current branch.

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 a pull request?

Automated code review for a pull request analyzes staged changes to identify bugs, security flaws, and performance issues. This process checks your code against best practices and project-specific architectural rules before merging.

Can I check staged git changes for security vulnerabilities before committing?

You can check staged git changes for security vulnerabilities by running an automated review. It inspects your diff against a comprehensive checklist, catching potential security flaws and deviations early in the development cycle.

Do I need the gh CLI to review code on a branch?

You need both git and the gh CLI installed to review code on a branch. These dependencies are required for diff generation and pull request inspection when performing automated code analysis.

What is the best way to enforce project-specific rules during code analysis?

The best way to enforce project-specific rules during code analysis is using a review process with contextual awareness. It integrates directly with your project architecture documents to evaluate code changes against your custom guidelines.

Does automated code review check for performance issues and best practices?

Automated code review does check for performance issues and best practices. It evaluates your staged changes against a comprehensive checklist that covers correctness, security, performance bottlenecks, and adherence to coding standards.