aif-review

Identify bugs, security issues, and performance problems in code changes.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-review-exsydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/ExsyDev/eye-blinking/tree/main/.claude/skills/aif-review
Command: npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-review-exsydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps developers perform thorough code reviews on staged changes or pull requests, catching bugs, security issues, performance problems, and best-practices gaps.

Core Features & Use Cases

  • Review Staged Changes: analyzes diffs in git (staged or unstaged) to surface issues before commits.
  • PR-Aware Review: fetches PR details and diffs when a PR number is provided.
  • Context Gate Checks: validates against architecture, coding standards, and roadmap constraints.
  • Actionable Feedback: produces a structured checklist of issues and suggested fixes.
  • Automation-friendly: integrates with CI or chat-based prompts when you say review code or similar.

Quick Start

Initiate a review of your changes by running /aif-review in your workspace.

Frequently Asked Questions about aif-review

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

FAQPage Schema
How do I review pull requests for security and performance issues before merging?▼

You can review pull requests for security and performance issues by analyzing staged or unstaged git diffs and PR data fetched via gh, which identifies bugs and produces a structured review checklist.

Can I check staged git changes against coding standards and architecture rules?▼

Yes, you can check staged git changes against coding standards and architecture rules by applying read-only context gates that validate diffs against your architecture and rules files before generating structured feedback.

What is the best way to automate code review for bugs in a CI pipeline?▼

The best way to automate code review for bugs in a CI pipeline is by processing git diffs and optional gh PR data to output a CI-friendly, structured checklist that surfaces bugs, security issues, and performance problems.

Does this code review tool work with both staged and unstaged git diffs?▼

Yes, this code review tool works with both staged and unstaged git diffs, analyzing the changes to surface bugs, security issues, performance problems, and best-practice gaps before you commit.

Do I need the gh CLI to review pull requests with this tool?▼

You need the gh CLI to fetch pull request details and diffs when providing a PR number, but you can still review local staged or unstaged git changes without it.