aif-review

Reviews code changes for correctness, security, performance, and maintainability using git and gh tooling.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/VeronikaVashkevich/job-tracking-app --skill aif-review-veronikavashkevich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/VeronikaVashkevich/job-tracking-app/tree/main/.opencode/skills/aif-review
Command: npx skills add https://github.com/VeronikaVashkevich/job-tracking-app --skill aif-review-veronikavashkevich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thoroughly review code changes for correctness, security, performance, and maintainability to reduce risk in software delivery.

Core Features & Use Cases

  • Without Arguments: review staged changes with git diff --cached, falling back to unstaged changes if nothing is staged.
  • With PR Number/URL: fetch PR details and diffs using gh CLI to review changes in PR context.
  • Context Gates & Project Context: check architecture rules and roadmap notes (.ai-factory/*) to surface potential policy or architectural issues.
  • Flexible routing: review by staged changes, PRs, or commits, with validation and guided prompts.

Quick Start

Run the /aif-review command to review the current branch's changes or a target PR.

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 for correctness and security before committing?

You can review staged changes by running the command without arguments, which uses git diff --cached to analyze code for security and correctness, automatically falling back to unstaged changes if nothing is staged.

Can I review a GitHub pull request using gh CLI for code maintainability?

Yes, you can review a GitHub pull request by providing the PR number or URL, which fetches PR details and diffs using the gh CLI to assess code maintainability and performance within the PR context.

How does automated code review handle project architecture rules and roadmap documents?

Automated code review checks project context gates by reading architecture rules and roadmap notes stored in the .ai-factory/* directory to surface potential policy or architectural conflicts in the code changes.

What is the best way to review multi-commit diffs for performance issues?

The best way to review multi-commit diffs is using flexible routing to target specific commits, fetching the context with git and gh tooling to analyze the changes for performance and maintainability issues.

Do I need to install additional dependencies to review code changes across commits?

No additional dependencies are required, but you need the gh and git tooling available in your environment to gather context and fetch diffs for reviewing code changes across staged changes, PRs, or commits.