aif-review

Automate code reviews on staged changes, pull requests, and commit ranges.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/marinkobabic/dario-shop --skill aif-review-marinkobabic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/marinkobabic/dario-shop/tree/main/.claude/skills/aif-review
Command: npx skills add https://github.com/marinkobabic/dario-shop --skill aif-review-marinkobabic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews are time-consuming, inconsistent, and often miss critical bugs, security flaws, and performance issues. This Skill automates the review process to catch issues early and enforce team coding standards.

Core Features & Use Cases

  • Multi-Source Review: Analyze staged local changes, GitHub pull requests, or commits between any two Git refs.
  • Comprehensive Checks: Evaluate code for correctness, security vulnerabilities, performance bottlenecks, best practice adherence, and test coverage.
  • Use Case: A developer can use this Skill to review their feature branch before opening a PR, or a tech lead can use it to validate a teammate's PR for merge readiness.

Quick Start

Use the aif-review skill to review all staged code changes in your current repository.

Frequently Asked Questions about aif-review

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

FAQPage Schema
How do I perform an automated code review on local Git changes before committing?

Automated code review on local Git changes analyzes staged code to identify bugs, security vulnerabilities, and performance issues. You can review staged local changes directly in your repository to catch issues early before opening a pull request.

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

Yes, automated code review can analyze GitHub pull requests to identify security vulnerabilities, performance bottlenecks, and best practice violations. It retrieves diffs and PR metadata using Git and GitHub CLI access to validate merge readiness.

Do I need GitHub CLI installed to run automated code reviews on my repository?

Yes, GitHub CLI access is required alongside Git to retrieve diffs and PR metadata for automated code reviews. These dependencies allow the review process to analyze pull request data and commit ranges across Git-based projects.

What is the best way to check code quality across a range of Git commits?

The best way to check code quality across Git commits is using automated code review to analyze the commit range between any two Git refs. This process evaluates correctness, security flaws, and best practice adherence for pre-merge validation.

Can I override static analysis rules for project-specific coding standards?

Yes, you can override static analysis rules for project-specific coding standards using skill-context configuration files. This allows teams to customize the automated code review checks to enforce their specific best practices and rules.