skills.rest
D4nitrix13
D4nitrix13COMMUNITY
Explore all skills by this author →
GitHub

pr-review

Review GitHub pull requests and leave categorized comments.

Updated Apr 9, 2025
Search Tags:#collaboration#workflow-automation#code-review#pr-review#github-pr#human-comments
One-click install
npx skills add https://github.com/D4nitrix13/dotfiles-tmp --skill pr-review-d4nitrix13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/D4nitrix13/dotfiles-tmp/tree/main/.config/opencode/skill/pr-review
Command: npx skills add https://github.com/D4nitrix13/dotfiles-tmp --skill pr-review-d4nitrix13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews GitHub PRs and leaves human, direct comments to help authors improve code quality and clarity.

Core Features & Use Cases

  • Fetch PR metadata and diffs to understand context.
  • Categorize issues into CRITICAL, NEEDS REVIEW, and QUESTION.
  • Compose humane, actionable review comments that invite collaboration.

Quick Start

Tell me to review a PR or share a PR URL, and I'll fetch its details and draft a thoughtful review.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate code review for a GitHub pull request?▼

To automate GitHub PR review, provide the pull request URL to trigger an automated fetch of metadata and diffs, categorize findings into CRITICAL or QUESTION levels, and generate human, actionable review comments.

What is the best way to leave human comments on a GitHub PR diff?▼

The best way to leave human comments on a GitHub PR is to fetch the diff, categorize issues into NEEDS REVIEW or CRITICAL, and compose respectful, context-aware messages that invite collaboration and improve code quality.

Can I review both small changes and large diffs in a GitHub pull request?▼

Yes, you can review both small changes and large diffs in a GitHub pull request by fetching the PR data to understand context and generating categorized, actionable review messages regardless of diff size.

How does categorizing PR findings into CRITICAL and QUESTION improve code review?▼

Categorizing PR findings into CRITICAL, NEEDS REVIEW, and QUESTION improves code review by organizing issues by severity, allowing authors to prioritize fixes clearly through direct, actionable, and respectful review comments.

Do I need to provide a PR URL to check my GitHub pull request?▼

Yes, you need to provide a PR URL or explicitly ask to review a GitHub pull request, which then fetches metadata and diffs using gh pr view and gh pr diff to generate thoughtful, categorized feedback.

Why are my GitHub PR review comments not inviting collaboration?▼

GitHub PR review comments may not invite collaboration if they lack context-awareness and categorization; generating humane, direct comments categorized as CRITICAL or QUESTION helps authors improve code quality and clarity.

Related Skills

Explore More Software Engineering Skills→
toumakidotoumakido

review-pr

Analyze GitHub pull requests and generate structured Markdown review briefings.

Community
Advanced
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
bennybennisonbennybennison

verification-loop

Run sequential build, type, lint, test, security, and diff checks.

Community
Intermediate
TECHKNOWMAD-LABSTECHKNOWMAD-LABS

security-audit

Scan code repositories for vulnerabilities and leaked secrets using static analysis tools.

Official
Advanced