kiro-review

Review code changes and output a structured markdown findings report.

13|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ulpi-io/browse --skill kiro-review-ulpi-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-review
Source: https://github.com/ulpi-io/browse/tree/main/.agents/skills/kiro-review
Command: npx skills add https://github.com/ulpi-io/browse --skill kiro-review-ulpi-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and review code changes using an independent AI agent.

Core Features & Use Cases

  • Automated diff analysis to surface key changes that matter for review.
  • Generates focused review prompts and a structured findings report for faster decision-making.
  • Supports iterative reviews by tracking previously resolved issues to avoid re-reporting.

Quick Start

Invoke kiro-review on your current branch to produce a focused AI review of code changes.

Frequently Asked Questions about kiro-review

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

FAQPage Schema
How do I run an AI code review on uncommitted branch changes?

You can automate pull-request verification by invoking kiro-review on your branch. It reads the diff, applies an independent AI agent to analyze code changes, and generates a structured findings report for pre-merge audits.

How does AI diff analysis work for pre-merge audits?

Yes, kiro-review supports iterative reviews by tracking previously resolved issues. This prevents the AI code review from re-reporting fixed problems across multiple review cycles on the same pull request.

Do I need kiro-cli installed to automate pull-request verification?

You need kiro-cli installed in your environment. The AI code review agent uses kiro-cli to read branch diffs and uncommitted changes, producing a markdown-ready findings report for pre-merge audits.

Can I track previously resolved issues in an iterative AI code review?

kiro-review distinguishes itself as an independent AI agent for code changes. Unlike basic linters, it generates focused review prompts and a structured findings report, providing a second opinion for branch reviews and pre-merge audits.

What is the best way to get a second opinion on code changes before merging?

To run an AI code review on uncommitted branch changes, invoke kiro-review on your current branch. It reads the diff and outputs a structured, markdown-ready findings report for faster decision-making.