skills.rest
bboymimi
bboymimiCOMMUNITY
Explore all skills by this author →
GitHub

pr-review

Fetch GitHub pull request data and generate detailed review reports in Obsidian.

Updated Aug 23, 2026
Search Tags:#code quality#code review#pull request#github#analysis#linus-style
One-click install
npx skills add https://github.com/bboymimi/claude-skills --skill pr-review-bboymimi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/bboymimi/claude-skills/tree/main/pr-review
Command: npx skills add https://github.com/bboymimi/claude-skills --skill pr-review-bboymimi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and templates (resource) components.

What problem does it solve?

This Skill automates the process of reviewing GitHub pull requests, providing detailed, Linus-style feedback to improve code quality and maintainability.

Core Features & Use Cases

  • Comprehensive Analysis: Fetches PR data, analyzes code changes commit-by-commit, and generates detailed review reports.
  • Contextual Understanding: Reads related source code to provide insightful feedback beyond superficial checks.
  • Use Case: When a teammate submits a complex PR, use this Skill to get a thorough, critical review that catches potential bugs, architectural issues, and performance bottlenecks before merging.

Quick Start

Use the pr-review skill to review pull request number 456 in the sched-ext/scx repository.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate rigorous pull request reviews for GitHub?▼

Automated pull request reviews fetch PR data and analyze code changes commit-by-commit to generate detailed reports. This process catches potential bugs, architectural issues, and performance bottlenecks before merging.

Can I focus my code review on security and performance only?▼

Yes, code review can be focused specifically on security, performance, architecture, or tests. This allows targeting specific dimensions of code quality rather than performing a generalized analysis of the changes.

How does a Linus-style code review analyze complex pull requests?▼

Linus-style code review analyzes complex pull requests by reading related source code for contextual understanding. It examines changes commit-by-commit to provide critical feedback beyond superficial checks.

Do I need a local repository path to analyze GitHub pull requests?▼

No, a local repository path is not strictly required, but the review process supports local repository path overrides. Configurable code reading depth also allows adjusting how deeply the analysis inspects the codebase.

What is the best way to save detailed code review reports?▼

Detailed code review reports are saved directly to Obsidian. This ensures that rigorous feedback, architectural notes, and performance analysis are documented for future reference and team alignment.

Are there limitations to automated pull request analysis?▼

Automated pull request analysis depends on fetching PR data and configurable code reading depth. Extremely large or disconnected repositories may limit contextual understanding if related source code cannot be accessed effectively.

Related Skills

Explore More Software Engineering Skills→
lexmountlexmount
19

pr-review-checklist

Generate Markdown PR review checklists from GitHub review threads and code context.

Official
Intermediate
glinckerglincker
35

pr-reviewer

Review pull requests for security, performance, test coverage, architecture, and style.

Official
Advanced
mathruffian-dotmathruffian-dot
70

codex-github-obsidian

Automate GitHub CLI operations and set up Obsidian MCPVault for collaborative note-taking.

Community
Advanced
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced