pr-review

Automating code review for GitHub pull requests involves parsing diffs and metadata to provide structured feedback across frontend, backend, and database domains. This Skill executes git and gh CLI commands to gather context and apply domain-specific checklists.

Multi-lens pull request analysis evaluates code through specific lenses for frontend, backend, database, and general software quality. It enforces project-specific standards like Hono route security, React hook correctness, and SQLite schema safety.

Yes, authenticated GitHub CLI access is required to review pull requests. The Skill requires authenticated access to the GitHub CLI and local git repository history to perform accurate code assessments.

Static analysis identifies missing RBAC middleware by applying domain-specific checklists to parsed pull request diffs. It automatically flags missing security logic before a human reviewer opens the PR.

Yes, you can use this automated code review for SQLite schema changes. The Skill's automated checklist specifically enforces SQLite schema safety alongside Hono route security and React hook correctness.

The limitations of automated pull request analysis include its dependency on local git repository history and the GitHub CLI. Without authenticated access and local context, it cannot perform accurate code assessments.