GitHub PR Review Skill
When asked to review a pull request:
Steps
- •
Fetch PR details:
bashgh pr view OWNER/REPO#NUMBER --json title,body,files,additions,deletions,commits gh pr diff OWNER/REPO#NUMBER
- •
Analyze the diff: Look at every changed file and understand what the PR does.
- •
Provide a structured review:
- •Summary: 2-3 sentences on what the PR does.
- •Key Changes: Bullet list of the most significant modifications.
- •Issues Found: Any bugs, logic errors, security concerns, or style problems.
- •Suggestions: Concrete improvements (with code snippets if helpful).
- •Verdict: Approve / Request Changes / Needs Discussion.
- •
Post the review back in Discord with a formatted message.
Notes
- •Be constructive, not nitpicky. Focus on things that matter.
- •If the PR is large, focus on the riskiest or most complex changes.
- •Reference specific file paths and line numbers when pointing out issues.