# Github Get Pr Comments

> Gather pull request review feedback and combine it with recent local project context so reviewer comments can be addressed efficiently.

- Skill: `lefant/github-get-pr-comments` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lefant/github-get-pr-comments`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lefant/github-get-pr-comments/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lefant (https://skillmd.com/u/lefant)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lefant/github-get-pr-comments

---


# GitHub Get PR Comments

Use this skill when the user wants reviewer feedback collected and organized before responding to or addressing a pull request review.

This skill is the replacement for the old `github_get_pr_comments` command.

## Dependencies

This skill depends on:
- `github-access` for GitHub API or `gh` usage
- `recent-context-from-git` patterns for recent local documentation context

## Workflow

1. Identify the PR:
   - use a provided PR URL or number
   - otherwise detect the PR from the current branch when possible
2. Fetch:
   - PR metadata
   - top-level review summaries
   - inline review comments
   - general PR comments
3. Gather local context:
   - recent devlogs
   - active plans
   - relevant specs and ADRs
   - uncommitted documentation changes if they explain current work
4. Present a unified summary grouped by:
   - blocking or required comments
   - suggestions
   - questions
   - supporting local context

## Output Shape

```markdown
## PR #{number}: {title}
**Branch**: {head} -> {base}
**Author**: {author}
**State**: {state}

### Comments to Address
- **Blocking**
- **Suggestions**
- **Questions**

### Local Context
- Recent devlogs and plans
- Relevant specs or ADRs
- Uncommitted docs explaining current state
```

## Notes

- If no PR can be inferred from the current branch, ask the user for the PR URL or number
- Prefer concise grouping over raw comment dumps