aif-review

Review staged Git changes and GitHub pull requests for bugs and security flaws.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/batFormat/sancrm-docs --skill aif-review-batformat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/batFormat/sancrm-docs/tree/main/.claude/skills/aif-review
Command: npx skills add https://github.com/batFormat/sancrm-docs --skill aif-review-batformat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of reviewing code for potential bugs, security vulnerabilities, performance issues, and adherence to best practices, ensuring higher code quality.

Core Features & Use Cases

  • Staged/Unstaged Code Review: Analyzes code changes that are currently staged or unstaged in your Git repository.
  • Pull Request Review: Reviews all changes within a specified GitHub pull request.
  • Comprehensive Checklist: Covers correctness, security, performance, best practices, and testing aspects.
  • Use Case: Before merging a feature branch, use this Skill to get an automated, detailed review of your code to catch potential issues early.

Quick Start

Review the code changes currently staged in your Git repository.

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 my staged Git changes?

Automated code review for staged Git changes analyzes your diffs to identify bugs, security flaws, performance bottlenecks, and deviations from best practices before merging.

Can I review a GitHub pull request for security and performance issues?

Yes, reviewing a GitHub pull request for security and performance issues is supported by retrieving PR data via the GitHub CLI and analyzing the changes against a comprehensive checklist.

What do I need to run an automated code review on my repository?

To run an automated code review on your repository, you need Bash, Git, and the GitHub CLI tools installed in your execution environment to analyze diffs and retrieve pull request data.

What is the best way to check code quality before merging a feature branch?

The best way to check code quality before merging a feature branch is to run an automated review on your staged or unstaged changes to catch potential bugs and ensure adherence to best practices.

Does the code review cover correctness and testing aspects?

Yes, the code review covers correctness and testing aspects, alongside security, performance, and best practices, providing a comprehensive analysis of your staged changes or pull requests.

When should I not use automated code review for my diffs?

You should not use automated code review for your diffs if your environment lacks Bash, Git, or the GitHub CLI, as these tools are strictly required for diff analysis and PR data retrieval.