fetching-pr-comments
Fetching PR Comments
Overview
Retrieve and parse GitHub PR review comments for the current branch using gh CLI.
Quick Reference
| Task | Command |
|---|---|
| Check if PR exists | gh pr view |
| View PR with issue comments | gh pr view --comments |
| Fetch review comments (code-level) | gh api repos/{owner}/{repo}/pulls/{n}/comments |
| Extract key fields | --jq '.[] | {path, line, body}' |
Workflow
-
Get PR number for current branch:
gh pr view --json number --jq '.number' -
Fetch review comments:
gh api repos/{owner}/{repo}/pulls/{n}/comments \ --jq '.[] | {path: .path, line: .line, body: .body}' -
Full command (single step):
gh api repos/OWNER/REPO/pulls/$(gh pr view --json number -q .number)/comments \ --jq '.[] | {path: .path, line: .line, body: .body}'
Important Distinctions
| Type | What it shows | How to get |
|---|---|---|
| Issue comments | PR-level discussion | gh pr view --comments |
| Review comments | Code-level feedback | gh api .../pulls/{n}/comments |
Common Patterns
Check if current branch has a PR:
gh pr view 2>/dev/null && echo "PR exists" || echo "No PR"
Get PR details + comments in one view:
gh pr view --comments
Fetch specific PR by number:
gh pr view 429 --repo owner/repo --comments
When NOT to Use
- Creating new PRs (use
gh pr create) - Reviewing diffs (use
gh pr diff) - Merging (use
gh pr merge)
More from bumgeunsong/daily-writing-friends
firebase-functions
Use when creating or modifying Firebase Cloud Functions in /functions directory. Enforces function structure and error handling patterns.
43pr-stacking
PR stacking workflow for breaking large features into smaller, dependent PRs. Use when planning multi-step features, creating dependent branches, or rebasing stacked changes.
29commit
Use when creating git commits in this project
28refactoring
Use when user explicitly asks to refactor code, or when test coverage is requested for untested code with side effects. Enforces Functional Core Imperative Shell pattern extraction before any changes.
28api-layer
Use when creating or modifying API functions in */api/ directories. Enforces Firestore patterns and data fetching conventions.
28code-style
Use when writing or modifying any code. Enforces naming conventions, function design, and code clarity principles.
28