github-code-review

Review code diffs and pull requests for correctness, security, and quality issues.

Updated May 14, 2026

Search Tags:#git #testing #code review #security #github #pull requests #inline comments

Ready to run

npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill github-code-review-sethypagna

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/github/github-code-review
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill github-code-review-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you evaluate code changes before they merge by turning diffs, pull requests, and local branch changes into clear review findings.

Core Features & Use Cases

Local Change Review: Inspect staged or branch-wide diffs with git to spot correctness, security, testing, and documentation issues before pushing.
Pull Request Review: Gather PR context, check changed files, and leave top-level or inline review comments on GitHub using gh or the REST API.
Structured Feedback: Produce consistent review summaries with critical issues, warnings, suggestions, and positive observations that are easy to act on.
Use Case: A developer asks for a pre-push review or a PR audit, and this Skill identifies risky code, missing tests, and cleanup opportunities in a format ready to share.

Quick Start

Ask the skill to review the current branch or a specific GitHub pull request and return a structured code review with inline comments if needed.

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 a GitHub pull request for security and correctness issues?▼

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.

Can I check my local git branch for code quality issues before pushing?▼

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.

What is the best way to automate structured code review feedback on GitHub PRs?▼

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.

Do I need GitHub authentication tokens to leave inline comments on a pull request?▼

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.

Does this code review approach work with local diffs and GitHub PR workflows?▼

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.

What limitations exist when reviewing code changes with inline comments?▼

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.