github-code-review

Analyze git diffs and annotate GitHub pull requests with structured feedback.

27|2|Updated Jan 15, 2024
One-click install
npx skills add https://github.com/erfanzar/Xerxes-Agents --skill github-code-review-erfanzar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/erfanzar/Xerxes-Agents/tree/main/src/python/xerxes/skills/github/github-code-review
Command: npx skills add https://github.com/erfanzar/Xerxes-Agents --skill github-code-review-erfanzar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently review code changes by analyzing diffs, generating structured feedback, and applying inline comments on pull requests to speed up safe merges.

Core Features & Use Cases

  • Pre-push checks to catch issues before they reach main.
  • Local diff analysis to understand changes across commits.
  • PR feedback workflow with inline comments via gh or GitHub REST API.
  • Flexible workflows that work with both the gh CLI and REST API when gh is unavailable.
  • Output structured review sections (Critical, Warnings, Suggestions, Looks Good) to standardize feedback.

Quick Start

Install prerequisites and run the pre-push review workflow to analyze changes before pushing.

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 on GitHub pull requests?

Automate code reviews by analyzing git diffs and posting inline PR comments via the gh CLI or GitHub REST API. This generates structured feedback to catch issues and speed up safe merges.

Can I run a local diff analysis before pushing code to main?

Yes, you can run a pre-push review workflow to analyze local code changes across commits. This allows you to catch issues and understand diffs before they reach the main branch.

What is the best way to structure pull request feedback for reviewers?

Structure pull request feedback into standardized sections: Critical, Warnings, Suggestions, and Looks Good. This categorizes diff analysis results to improve review quality and clarity.

Does this code review automation work without the gh CLI installed?

Yes, the workflow supports both the gh CLI and the GitHub REST API. It falls back to REST API calls to annotate pull requests with inline comments when gh is unavailable.

How do inline comments improve pull request review quality?

Inline comments map structured feedback directly to specific lines of code in the git diff. This pinpoints exact issues within the pull request, making the review process more efficient.