aif-review

Analyze git diffs, pull requests, or commit ranges for security and performance issues.

Updated Jul 15, 2026

Search Tags:#automation #git #static analysis #code review #pull request #security

Ready to run

npx skills add https://github.com/o2b3k/idomarketingbot --skill aif-review-o2b3k

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/o2b3k/idomarketingbot/tree/main/.claude/skills/aif-review
Command: npx skills add https://github.com/o2b3k/idomarketingbot --skill aif-review-o2b3k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the tedious and error-prone process of manual code review, ensuring that security, performance, and best-practice standards are consistently applied across your codebase.

Core Features & Use Cases

Multi-Mode Review: Analyze staged changes, specific pull requests, or entire commit ranges with a single command.
Context-Aware Gates: Automatically validates changes against project-specific architecture, rules, and roadmap artifacts.
Validation Pass: Use the optional check flag to trigger a secondary subagent that filters and reclassifies findings for higher accuracy.

Quick Start

Run the aif-review skill to perform a comprehensive code review on your currently staged changes.

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?▼

You can automate code review by analyzing git diffs and pull requests for security vulnerabilities and performance bottlenecks. The skill processes staged changes to provide actionable, merge-blocking feedback based on project-specific rules.

What does context-aware static analysis check during a git diff review?▼

Context-aware static analysis checks git diffs for security vulnerabilities, performance bottlenecks, and maintainability issues. It validates changes against project-specific architecture and rule artifacts to enforce consistent coding standards.

Can I run an automated code review on staged changes before creating a pull request?▼

Yes, you can run an automated code review on currently staged changes before creating a pull request. The multi-mode analysis evaluates staged files directly against your project's architecture and roadmap artifacts.

How do I filter out false positives from automated static analysis findings?▼

You can filter false positives from automated static analysis by using the optional validation check flag. This triggers a secondary subagent that filters and reclassifies findings through a multi-stage validation process for higher accuracy.

Do I need to configure project-specific rules before running an automated code review?▼

Providing project-specific architecture and rule artifacts is optional but recommended. These artifacts allow the automated code review to enforce consistent coding standards tailored to your codebase.

What is the best way to review an entire commit range for security vulnerabilities?▼

The best way to review an entire commit range for security vulnerabilities is using multi-mode automated code review. It analyzes the specified commit range against project rules and applies a validation pass to filter findings.