name: reviewing-code description: Rigorously reviews changes, commits, PRs, and patches. Use when asked to review code, a PR, a diff, changes, or when the user says "review", "code review", or "look over this" or similar. license: AGPL-3.0-or-later metadata: author: Amolith amolith@secluded.site

Run a code review using the preferred tool.

Selection

If a native code review tool is already available, use it directly. Otherwise, prefer the following in this order:

command -v kodus; command -v coderabbit; command -v amp

If CodeRabbit is rate-limited, use another. If none are usable, tell the user and stop.

CLI usage

kodus review --prompt-only --staged
kodus review --prompt-only --branch main # Compare changes against branch
kodus review --prompt-only --commit abc123
kodus review --prompt-only src/auth.ts

coderabbit review --prompt-only # all changes
coderabbit review --prompt-only --type committed
coderabbit review --prompt-only --type uncommitted
coderabbit review --prompt-only --base main

amp review  # uncommitted changes
amp review "HEAD~1"
amp review "main...HEAD"
amp review -f src/auth.ts
amp review -i "explicit, detailed instructions to focus on something(s) in particular"

Output

Display issues as a numbered list:

1. category (severity) - [file-basename](file-path#range): verbatim finding from the code review tool

Then ask:

• If other code review tools are available: "Would you like me to fix any of these issues, rerun that, run it differently, or check with [Kodus, CodeRabbit, or Amp] as well?", only listing the available options
• If only the one is: "Would you like me to fix any of these issues, rerun that, or run it differently?"

If told to fix anything, do so, then go through the same review flow again and stop to present the follow-up review.