# Agent Pull Request Review Comments and Unresolved Threads
Status: public
Confidence: medium (0.685) (verified)
Last verified: 2026-06-03
Generation: ai_structured


## TL;DR

Agents fixing pull requests need review comments, requested changes, unresolved threads, and line-level context before deciding what to edit.

## Core Explanation

Pull request review data is a high-frequency agent source because it encodes human intent, blocking feedback, suggested patches, and acceptance criteria. A useful agent should distinguish top-level PR discussion from inline file comments and review submissions.

The agent should preserve thread identity, file path, line range, diff side, outdated status, author, timestamp, and resolution state. It should not treat every comment as an instruction; approvals, requests for changes, resolved threads, and stale comments have different operational meaning.

## Source-Mapped Facts

- GitHub documentation says pull request reviewers can comment on changes, suggest improvements, approve, or request changes before code is merged. ([source](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews))
- GitHub documentation says review comments can be made on specific lines and conversation threads can be marked resolved to track addressed feedback. ([source](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews))
- GitHub's GraphQL API reference includes PullRequestReviewThread as a pull request review conversation thread object. ([source](https://docs.github.com/en/graphql/reference))

## Further Reading

- [GitHub About Pull Request Reviews](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)
- [GitHub GraphQL API Reference](https://docs.github.com/en/graphql/reference)