aif-review

Reviews git staged changes and pull requests for bugs, security issues, performance problems, and maintainability via CLI tools.

Updated Mar 23, 2024
One-click install
npx skills add https://github.com/Ard2p/sk-bar-site --skill aif-review-ard2p
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/Ard2p/sk-bar-site/tree/main/.cursor/skills/aif-review
Command: npx skills add https://github.com/Ard2p/sk-bar-site --skill aif-review-ard2p

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates comprehensive code reviews of staged changes or pull requests, catching bugs, security issues, performance problems, and maintainability concerns.

Core Features & Use Cases

  • Load and honor project configs to align with architecture, rules, and roadmaps.
  • Analyze changes across staged files or diffs, PRs, and commits.
  • Provide structured feedback, safety checks, and actionable recommendations for developers.

Quick Start

Review the currently staged changes by running /aif-review

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 reviews for pull requests to check for bugs and security issues?

Automated code review analyzes staged changes or pull requests to detect bugs, security issues, performance problems, and maintainability concerns. It fetches diffs and metadata using git and GitHub CLI tools to provide structured feedback and safety checks.

Can I review staged git changes before creating a commit?

Yes, you can review staged git changes before committing by running the review command directly. It analyzes the staged files and diffs to provide actionable recommendations and safety checks based on your project configurations.

Do I need to install GitHub CLI and git to review pull requests?

Yes, git and GitHub CLI tools are required dependencies to fetch diffs and metadata for reviewing pull requests. These tools allow the review process to access branch commits and apply optional config-driven gates for comprehensive analysis.

What is the best way to ensure code maintainability when reviewing diffs?

The best way to ensure maintainability when reviewing diffs is to load and honor project configs that align with your architecture and rules. This ensures the automated review provides structured feedback tailored to your specific roadmap.

Can I apply config-driven gates to code reviews on any git branch?

Yes, config-driven gates can be applied to code reviews on any git branch. This feature allows you to enforce specific architecture rules, safety checks, and project standards when analyzing commits or pull requests.