aireview

Review source code changes and report high-confidence bugs as severity-tagged notes.

20|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/radareorg/radare2-skills --skill aireview-radareorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aireview
Source: https://github.com/radareorg/radare2-skills/tree/main/dev/aireview
Command: npx skills add https://github.com/radareorg/radare2-skills --skill aireview-radareorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review source code changes in commits, functions, or files and produce only high-confidence, actionable findings in a consistent format.

Core Features & Use Cases

  • Context-aware review: Gathers relevant code and change context before assessing issues.
  • Focused security and correctness checks: Targets potential bugs, security concerns, functional correctness, and API contract violations.
  • Structured, low-noise output: Emits severity-tagged task notes with concise, constructive, max-2-sentence issue descriptions.

Quick Start

Use the aireview skill to review the changed files in the provided commit or pull request and produce high-confidence severity-tagged findings.

Frequently Asked Questions about aireview

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

FAQPage Schema
How do I review pull request diffs for security and correctness issues?

To review pull request diffs for security and correctness, the skill analyzes changed lines in commits or files to identify high-confidence bugs, security concerns, and API contract violations. It gathers relevant change context before assessing potential functional issues.

What is the best way to perform automated static analysis on source code changes?

Automated static analysis on source code changes is performed by targeting only modified lines within branches or pull requests to ensure focused diff inspection. This approach limits comments to high-confidence findings and reports them as structured severity-tagged task notes.

Can I use radare2 for code review on specific commits and functions?

Yes, you can use radare2 for code review on specific commits and functions. The skill evaluates targeted source code changes to produce high-confidence, actionable findings in a consistent format, focusing its checks strictly on the modified lines within those commits or functions.

How does diff inspection handle false positives during code review?

Diff inspection handles false positives during code review by enforcing a high-confidence threshold before reporting any findings. It limits comments to only high-certainty issues and emits concise, constructive descriptions with severity tags to maintain low-noise output.

What format does automated code review output use for identified bugs?

Automated code review output for identified bugs uses a structured format consisting of severity-tagged task notes. Each finding includes a concise, constructive issue description limited to a maximum of two sentences to ensure actionable and low-noise reporting.