Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.
90
89%
Does it follow best practices?
Impact
85%
1.06xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Inline vs PR-level comment distinction
Inline comments endpoint
100%
100%
PR-level comments endpoint
38%
100%
Does NOT rely solely on gh pr view --comments
100%
100%
Accepts PR number argument
100%
100%
Accepts optional repo argument
100%
100%
Explanation covers comment type distinction
100%
100%
Explanation covers gh pr view limitation
100%
100%
Separate output sections
100%
100%
Correct endpoint path format
60%
100%
EXPLANATION.md file present
100%
100%
Script is a bash script
100%
100%
Unresolved comment workflow using gh-pr-info
Uses gh-pr-info script
0%
0%
Repo auto-detection
100%
100%
Optional repo argument
100%
100%
GraphQL-based filtering referenced
100%
100%
Workflow step: get unresolved comments first
100%
100%
Workflow step: make fixes in local branch
100%
100%
Excludes resolved/collapsed/dismissed
80%
100%
PR number argument
100%
100%
Script is a bash script
100%
100%
WORKFLOW.md file present
100%
100%
gh-pr-info repo argument forwarded
0%
0%
Comprehensive PR status and CI reporting
CI checks command
100%
0%
Files changed endpoint
0%
100%
PR-level comments endpoint
100%
100%
PR number argument
100%
100%
Optional repo argument
100%
100%
Repo auto-detection
100%
100%
CI failures highlighted
100%
100%
gh-pr-info delegation
87%
100%
Structured report sections
100%
100%
Failed CI log command
0%
0%
Script is a bash script
100%
100%
aed1afb
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.