readability-review

You can automate code readability and style guide checks by running parallel review agents that fetch GitHub PR diffs, classify Unity C# and shader files, and post high-confidence violations as a concise comment.

Yes, automated PR review skips vendor and third-party code by classifying files by extension and filtering them out before applying bundled style guides and CLAUDE.md guidance to the remaining changes.

GitHub pull request reviews handle low-confidence style violations by scoring each finding from 0–100 and filtering out low-confidence or pre-existing problems before posting only validated, cite-backed issues.

Yes, you can review shader file changes by applying bundled per-language style guides from the references directory to matching file types in the PR diff, ensuring only relevant style rules are enforced.

You need gh access to fetch PR diffs and post review comments, along with bundled reference style guides and CLAUDE.md guidance to direct the parallel review agents and confidence scoring.

You should use automated readability scoring when you want to catch clear style violations and reduce noisy or ambiguous feedback on Unity repository PRs before maintainers perform manual code review.