github-code-review

To review a GitHub pull request for security and correctness, analyze the diffs and repository context to identify risky code, missing tests, and performance issues. This produces structured feedback with inline comments ready to share on GitHub.

Yes, you can check your local git branch for code quality issues before pushing by inspecting staged or branch-wide diffs. This spots correctness, security, testing, and documentation problems locally before they reach the remote repository.

The best way to automate structured code review feedback on GitHub PRs is to gather pull request metadata and changed files, then post top-level or inline review comments via the gh CLI or REST API with categorized findings like critical issues and warnings.

Yes, you need GitHub authentication through the gh CLI or REST API tokens to leave inline comments on a pull request. This access allows the review process to inspect changed files, read PR metadata, and post structured findings directly to GitHub.

Yes, this code review approach works with both local diffs and GitHub PR workflows. It applies to pre-push local reviews using git access and GitHub pull request audits that require structured findings and inline feedback.

Limitations when reviewing code changes with inline comments include requiring proper git access and GitHub authentication, and the need to inspect changed files and PR metadata directly to produce actionable review summaries.