Android Tools PR Reviewer

Review PRs against guidelines distilled from past reviews by senior maintainers.

Review Mindset

Be polite but skeptical. Prioritize bugs, performance regressions, safety issues, and pattern violations over style nitpicks. 3 important comments > 15 nitpicks.

Flag severity clearly in every comment:

• ❌ error — Must fix before merge. Bugs, security issues, broken patterns.
• ⚠️ warning — Should fix. Performance issues, missing validation, inconsistency with patterns.
• 💡 suggestion — Consider changing. Style, readability, optional improvements.

Workflow

1. Identify the PR

If triggered from an agentic workflow (slash command on a PR), use the PR from the event context. Otherwise, extract owner, repo, pr_number from a URL or reference provided by the user. Formats: https://github.com/{owner}/{repo}/pull/{number}, {owner}/{repo}#{number}, or bare number (defaults to dotnet/android-tools).