github-code-review

Review GitHub pull request diffs and submit inline comments.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill github-code-review-marblesodas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill github-code-review-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you catch bugs, security issues, and quality regressions early by turning Git diffs and GitHub pull requests into structured review feedback.

Core Features & Use Cases

  • Local pre-push review: Review staged changes or compare against main using git diff and focused checks (security, correctness, quality).
  • GitHub PR review: Fetch PR details, list changed files, check out the PR branch, and leave both summary and inline comments.
  • Structured outputs and workflows: Produce consistent feedback sections (Critical/Warnings/Suggestions/Looks Good) and submit APPROVE/REQUEST_CHANGES/C0MMMENT reviews.

Quick Start

Ask the skill to review PR #123 on GitHub and comment inline on the files and lines that need attention.

Frequently Asked Questions about github-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review pull requests with inline comments on GitHub?

Review pull requests by fetching PR metadata and analyzing Git diffs to post structured summary and inline comments directly on files. Use the gh CLI or direct REST calls to submit APPROVE, REQUEST_CHANGES, or COMMENT reviews.

Can I review staged Git changes locally before pushing to a remote repository?

Review staged Git changes locally before pushing by running focused checks against your diff. Compare staged changes against the main branch to identify security issues, correctness bugs, and quality regressions early.

What is the best way to automate code review checks for security and correctness?

Automate code review checks by analyzing pull request diffs and inline issues to produce structured feedback. Generate consistent output sections for Critical, Warnings, Suggestions, and Looks Good to catch bugs and security vulnerabilities.

Do I need authenticated GitHub access to post inline comments on a pull request?

Authenticated GitHub access is required to post inline comments on a pull request. The review workflow needs a local git repository context and uses either the gh CLI or direct REST calls to view PRs and submit review feedback.

How does a GitHub PR review workflow handle checking out branches and listing changed files?

The GitHub PR review workflow fetches PR details, lists changed files, and checks out the PR branch locally. It analyzes the Git changes to generate actionable feedback before submitting summary and inline comments to GitHub.

What are the limitations of using local git diff for pre-push code review?

Local git diff review is limited to analyzing staged changes or comparisons against main without full GitHub PR metadata. It catches security and quality issues locally but cannot post inline comments or fetch remote PR context.