github-code-review

Analyze git diffs and generate inline comments on GitHub PRs.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/AlexiosBluffMara/mercury --skill github-code-review-alexiosbluffmara
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/AlexiosBluffMara/mercury/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/AlexiosBluffMara/mercury --skill github-code-review-alexiosbluffmara

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code review is time-consuming and inconsistently applied across teammates. This skill automates the process by analyzing diffs, generating inline feedback, and guiding pre-push and PR reviews to ensure consistent quality.

Core Features & Use Cases

  • Review local changes (pre-push) by inspecting diffs and summarizing issues.
  • Review open PRs on GitHub via gh or REST calls, with structured inline comments and a formal review flow.
  • Produce a clear, actionable feedback format that can be pasted into PR comments or reviews.

Quick Start

Run a local pre-push review on your current changes to generate a structured feedback report.

Frequently Asked Questions about github-code-review

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

FAQPage Schema
How do I automate code reviews for pull requests on GitHub?

You can automate code reviews by analyzing git diffs and generating inline comments on pull requests. This skill uses the gh CLI or falls back to git and curl to perform thorough PR reviews with structured, deterministic feedback.

Can I review local git changes before pushing to a remote repository?

Yes, you can review local changes pre-push by inspecting git diffs and summarizing issues. This process generates a structured feedback report to ensure code quality before pushing your commits.

Do I need the gh CLI installed to review open GitHub PRs with inline comments?

No, you do not need the gh CLI strictly required, as the skill falls back to git and curl using REST APIs. However, you must have repository access and appropriate authentication configured to generate inline comments.

What is the best way to generate structured inline comments for a code review?

The best way to generate structured inline comments is by analyzing git diffs through an automated review workflow. This skill produces clear, actionable feedback formatted for direct use in PR comments and reviews.

Are there limitations when automating pre-push code reviews with standard CLI tools?

Automating pre-push code reviews relies on standard CLI tools and REST APIs without hardcoded credentials, meaning it cannot operate without proper user authentication. You must ensure repository access is configured for the review process to work.