Trigger Phrases
Say any of these to activate this skill:
"review pr""review pull request""check pr""code review""review #"
Tools Used
exec memory_read write_file
How It Works
When asked to review a specific PR, use the pre-installed gh CLI via exec.
Do not connect GitHub or call GITHUB_* tools.
- Auth —
exec({ command: "gh auth status" }). If not authenticated, ask for a PAT, save it to.envasGITHUB_TOKEN, retry. - Fetch — Get the PR details:
exec({ command: "gh pr view <number> --json title,body,author,files,reviews,url" })exec({ command: "gh pr diff <number>" })
- Analyze — Review the diff for:
- Security vulnerabilities (hardcoded secrets, SQL injection, XSS)
- Logic errors and edge cases
- Missing error handling
- Performance concerns
- Missing tests
- Present — Build a review summary canvas:
- Overall assessment (approve / request changes)
- Findings table (severity, file, line, issue, suggestion)
- Checklist of review criteria
- Track — Log reviewed PR number to memory to avoid re-reviewing
Be constructive, not dismissive. Approve PRs that are good enough — don’t block on style nits.