aif-review

Reviews staged changes, pull requests, or commit ranges for bugs, security, and performance issues.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-review-1t1scool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/1t1sCooL/zazyvala-bot/tree/main/.cursor/skills/aif-review
Command: npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-review-1t1scool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing code changes is time-consuming and error-prone, especially when checking staged diffs, pull requests, or long commit ranges against project conventions. This Skill automates structured code review with a consistent checklist covering correctness, security, performance, and best practices. ## Core Features & Use Cases - Multi-Mode Review: Review staged changes, a GitHub pull request by number or URL, or all commits between a git ref and HEAD. - Context Gates: Cross-checks findings against project architecture, rules, and roadmap artifacts for convention and milestone alignment. - Project-Specific Rules: Loads accumulated project-level review rules from skill-context files that override general defaults. - Use Case: Before merging a feature branch, run the review against the base branch to get per-commit feedback, a risk-level summary, and a prioritized list of critical issues and suggestions. ## Quick Start Ask the assistant to review your staged changes or a specific pull request, for example by saying: review my staged changes or review PR 123.

Frequently Asked Questions about aif-review

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

FAQPage Schema
How do I review staged changes before committing?

Invoke the review with no arguments to analyze staged changes via git diff --cached. If nothing is staged, it falls back to unstaged changes and produces a structured summary with critical issues, suggestions, and a risk level.

How do I review a GitHub pull request from the command line?

Pass the PR number or URL as the argument. The review uses gh pr view and gh pr diff to fetch details and the diff, then checks all changes against correctness, security, performance, and best-practice checklists.

Can I review all commits on a branch compared to main?

Yes, pass a branch, tag, or commit ref as the argument to enter commits mode. It lists commits between the ref and HEAD, reviews each one individually, and asks before proceeding if there are more than 20 commits.

What happens if I pass an invalid git ref to the review?

The argument is validated with git rev-parse --verify. If invalid, the review does not silently fall back to staged changes; it asks whether to review staged changes instead or cancel.

Does the code review check project-specific conventions?

Yes, it reads project context gates including architecture, rules, and roadmap artifacts, plus a skill-context file with accumulated project rules. Project-specific rules override general review defaults when they conflict.