skills.rest
cryptopafi
cryptopafiCOMMUNITY
Explore all skills by this author →
GitHub

github-code-review

Review git diffs and GitHub pull requests with structured feedback.

1|Updated Apr 12, 2026
Search Tags:#git#code review#pull request#github#diff#pre-push#inline comments
One-click install
npx skills add https://github.com/cryptopafi/nexusos-skills --skill github-code-review-cryptopafi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/cryptopafi/nexusos-skills/tree/main/github/github-code-review
Command: npx skills add https://github.com/cryptopafi/nexusos-skills --skill github-code-review-cryptopafi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and reviewers catch bugs, security issues, and quality regressions before code is merged by analyzing git diffs, applying a review checklist, and producing structured feedback for maintainers and contributors.

Core Features & Use Cases

  • Review local staged changes or full branch diffs and produce a prioritized summary of critical issues, warnings, suggestions, and positives.
  • Inspect and interact with GitHub pull requests using the gh CLI or fall back to the REST API via curl to list changed files, view diffs, check out branches, leave inline comments, and submit formal reviews.
  • Pre-push workflow to detect secrets, debug statements, merge conflicts, large accidental files, missing tests, and common security or performance problems.

Quick Start

Use the github-code-review skill to review the current branch changes and produce a Code Review Summary with critical issues, warnings, suggestions, and items that look good.

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 local git diffs before pushing a branch?▼

Review local git diffs by analyzing staged changes or full branch diffs to produce a prioritized summary of critical issues, warnings, suggestions, and positives before pushing.

Can I leave inline review comments on a GitHub pull request?▼

Yes, you can leave inline comments on GitHub pull requests using the gh CLI or the REST API to list changed files, view diffs, check out branches, and submit formal atomic reviews.

Does a pre-push code review checklist catch secrets and debug statements?▼

A pre-push code review checklist detects secrets, debug statements, merge conflicts, large accidental files, missing tests, and common security or performance problems before code is merged.

What do I need to interact with GitHub pull requests for code reviews?▼

You need a local git repository and GitHub authentication to interact with remote GitHub pull requests via the gh CLI or REST API for listing files and leaving comments.

What is the best way to structure actionable feedback for a pull request diff?▼

Structure actionable feedback by applying a review checklist to the diff and generating a prioritized Code Review Summary containing critical issues, warnings, suggestions, and items that look good.

When should I not use an automated pre-push code review?▼

Avoid automated pre-push code review when you lack a git repository or GitHub authentication, as the review process requires local diffs or API access to inspect changes and submit comments.

Related Skills

Explore More Software Engineering Skills→
liumeixinliumeixin
4

github-pr-workflow

Automate the GitHub Pull Request lifecycle using gh CLI or git and REST API.

Community
Advanced
ProyectoG007ProyectoG007

glab-mr

Manage GitLab merge requests from creation to merging.

Community
Intermediate
xxihxxih
1

springboot-verification

Validate Spring Boot applications with build, static analysis, coverage, and security scans.

Community
Advanced
webn77webn77

bs-detector

Analyze code snippets for hardcoded secrets and quality issues.

Community
Intermediate