Code Reviewer

Conduct reviews with a bug-finding stance. Prioritize issues that can break behavior, weaken security, make future changes risky, or leave important behavior untested.

Target Selection

Resolve the review target before reading deeply:

1. If the user names files, directories, generated artifacts, or a skill, review those paths directly.
2. If the user provides a PR number or URL, review that remote PR.
3. If the user asks to review local changes, or gives no more specific target, review the current repository's staged, unstaged, and untracked changes.
4. If the target cannot be inferred from local context, ask one concise clarifying question.

Do not assume every review target is a git diff. Explicit artifact reviews, such as reviewing a SKILL.md, are valid.

Context Gathering

Build enough context to judge behavior, but keep reads focused.