code-review

Audit GitHub pull requests and generate structured review reports.

3|2|Updated Nov 12, 2017
One-click install
npx skills add https://github.com/ntsk/dotfiles --skill code-review-ntsk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ntsk/dotfiles/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/ntsk/dotfiles --skill code-review-ntsk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, read-only workflow for reviewing pull requests using the GitHub CLI, reducing time spent on manual checks and comments.

Core Features & Use Cases

  • PR Overview: Retrieve PR metadata (title, author, base/head) to get context fast.
  • Diff Review: See changes via gh pr diff to assess impact.
  • CI & Checks: Inspect CI results with gh pr checks.
  • Impact Analysis: Identify potential callers and integration points.

Quick Start

For example, run gh pr view 123 to fetch details, then gh pr diff 123 to review changes, and gh pr checks 123 to verify CI status.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a GitHub pull request using the command line?

Review pull requests using GitHub CLI commands: gh pr view to see PR metadata, gh pr diff to examine code changes, and gh pr checks to verify CI status. This read-only workflow retrieves all review data without manual GitHub web navigation.

Can I automate PR auditing and summarize changes across multiple pull requests?

Yes. This Skill audits and summarizes GitHub PRs by retrieving overviews, diffs, and CI check results through GitHub CLI, then produces a structured review report. Automate repetitive review steps for open-source and private repositories.

What information can I extract from a pull request using GitHub CLI?

GitHub CLI provides PR metadata (title, author, base/head branches), full diffs to assess code impact, CI and check status, and integration points. These read-only operations feed impact analysis and structured findings without modifying the repository.

Does GitHub CLI work for reviewing pull requests in private repositories?

Yes. GitHub CLI read-only operations (GET via gh api, gh pr view/diff/checks) work in both open-source and private repositories, enabling consistent PR review workflows across repository types.

What's the fastest way to check CI status and review code changes on a PR?

Run gh pr view to fetch PR context, gh pr diff to review changes in one command, and gh pr checks to inspect CI results. This streamlined sequence reduces manual checks and comment time on GitHub's web interface.

Can I identify which files and functions are affected by a pull request?

Yes. The gh pr diff command reveals all code changes, enabling impact analysis to identify potential callers, integration points, and affected modules without leaving the command line.