code-review-resolver

You can automatically resolve GitHub PR review comments by analyzing commit history and agent context to identify resolved threads. This process maps review comments to threads and applies GraphQL mutations to close eligible conversations automatically.

Yes, you can run a dry-run preview to see which pull request threads the analysis identifies as eligible for resolution. This allows you to verify the commit history and agent context mapping before applying any automatic thread changes.

Resolving GitHub PR review threads requires the GraphQL API to apply mutations that close the conversations. The REST API is also utilized alongside GraphQL for fetching PR review comments and mapping them to their respective threads.

The best way to reduce manual code review overhead is to use an automated bot that analyzes commit history and agent context. It determines which feedback has been addressed and automatically resolves the corresponding review threads.

The available methods for determining resolved status are commit-history analysis and agent-context analysis. Both methods evaluate the pull request state to identify which review threads have been successfully addressed.

Yes, you can configure the resolution scope when auto-resolving pull request review comments. This allows you to control which threads the bot targets, alongside options for dry-run previews and optional auto-resolve workflows.