aif-review

Analyze staged changes or GitHub pull requests for issues and security gaps.

83|5|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-review-artemyurov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/ArtemYurov/TomoBar/tree/main/.claude/skills/aif-review
Command: npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-review-artemyurov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines code quality reviews by guiding the user through a structured checklist that evaluates correctness, security, performance, and maintainability for staged changes and pull requests.

Core Features & Use Cases

  • Staged Changes Review: analyzes diffs in git index to surface bugs, security gaps, and improvement opportunities before committing.
  • PR Review: fetches PR details and diffs to provide comprehensive feedback across changes.
  • Checklist-driven Analysis: covers correctness, security, performance, best practices, and maintainability to standardize reviews.

Quick Start

Ask the assistant to review the current changes or a PR by providing the PR number or URL.

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 git changes for security and performance issues?

Analyze staged git changes using a structured checklist to identify bugs, security gaps, and performance problems before committing. The review evaluates correctness, security, performance, and maintainability across the diff, then reports findings with suggested fixes and next steps.

Can I use a checklist to review a GitHub pull request?

Yes, you can review a GitHub pull request by fetching the PR details and diffs using the PR number or URL. The checklist-driven analysis covers correctness, security, performance, best practices, and maintainability to provide comprehensive feedback across the changes.

What is the best way to automate code quality reviews for pull requests?

Automate code quality reviews by fetching PR diffs and evaluating them against a structured checklist for correctness, security, performance, and maintainability. This surfaces bugs and improvement opportunities, reporting findings in a clear, actionable format with suggested fixes and next steps.

Does static analysis for code review work with local git diffs?

Yes, static analysis for code review works with local git diffs by analyzing staged changes in the git index. It surfaces bugs, security gaps, and improvement opportunities before you commit, handling local diffs with the same structured checklist used for pull requests.

What does a checklist-driven code review cover for staged changes?

A checklist-driven code review covers correctness, security, performance, best practices, and maintainability for staged changes. It standardizes reviews by evaluating git index diffs and reporting findings in a clear, actionable format with suggested fixes and next steps.

When do I need to review staged changes instead of the full pull request?

Review staged changes when you want to surface bugs, security gaps, and improvement opportunities before committing to git. Analyzing the local diff in the git index lets you catch issues early, whereas a PR review provides comprehensive feedback across all committed changes.