pr-review

Provide the PR URL or number and the review fetches it with gh pr view and gh pr diff, reads each changed file in full, and returns a severity-scored findings table. Local branches are reviewed by diffing against origin/main.

Changed paths are mapped to their library and platform first, then the matching rules are applied: Tailwind conventions for libs/ui-react and useStyleSheet conventions for libs/ui-rnative. When both platforms are touched, an API-parity check compares prop names, defaults, and variants.

No. Issues already enforced by ESLint, such as banned imports, import ordering, type-style rules, and formatting, are explicitly excluded. The review focuses on problems a linter cannot catch, like wrong abstractions or raw Tailwind colors instead of design tokens.

If production code under libs/*/src changed without a version plan, it is reported as a Major 8/10 finding in the Release category. Non-patch bump types, multi-package plan files, and wrong package names are flagged as Moderate 6/10.

Yes. Zero findings is an explicitly valid result, and the review will say so and recommend approval. Findings are never padded or speculative; every reported issue must cite a concrete file and line.