github-code-review

Review a GitHub pull request by inspecting diffs and changed files to produce structured code quality feedback. The Skill generates summary plus inline comments and submits formal verdicts like approve, request changes, or comment using gh or REST API.

Yes, you can review local git diffs before pushing by analyzing staged changes or comparisons against the main branch. The Skill evaluates these pre-push diffs to find issues and summarizes findings for early code quality checks.

Leave inline comments on a GitHub PR by inspecting changed files in the diff and mapping findings into severity tags. The Skill submits these inline notes along with a summary review event via authenticated gh or REST API calls.

Yes, GitHub code review requires authenticated access via a GitHub token using either the gh command or REST API. This authentication is necessary to view PR details, inspect diffs, and submit review events.

Categorize code review findings by severity using a checklist-driven evaluation that maps issues into Critical, Warning, Suggestion, and Looks Good sections. This structured approach turns diffs into clear, prioritized feedback before merging.

You can submit formal review verdicts to approve, request changes, or comment on a GitHub PR. The Skill completes this end-to-end workflow by submitting the review event through either the gh or REST API.