resolve-pr-threads

To automatically resolve fixed GitHub PR review threads, you need a workflow that verifies each comment's referenced issue against the current code diff before closing it. This Skill confirms the issue is actually addressed in the updated file and line context before executing the resolve mutation.

Safe pull request thread resolution requires strict non-resolution on ambiguous or partially addressed cases. This approach prevents incorrect thread closure from hiding unresolved comments by only resolving threads when the updated code verifiably confirms the issue was addressed.

You can configure automated bot workflows to resolve only their own PR threads by setting the THREAD_RESOLVE_SCOPE parameter to 'own'. This scoping control supports resolving across all reviewers, only bot-authored threads, or skipping entirely via the 'none' option.

Resolving GitHub review threads via GraphQL can leave an audit trail by posting an AI-autogenerated justification reply before calling the resolveReviewThread mutation. This audit-friendly comment includes a rationale and an optional commit reference explaining the closure.

GitHub pull request review threads remain unresolved during automated maintenance when the referenced issue is ambiguous or only partially addressed in the current diff. The process strictly avoids resolving threads that lack verifiable evidence of the fix to prevent hiding open comments.

Yes, you need GraphQL pagination to retrieve all review threads before resolving them. The process requires fetching the complete list of reviewThreads associated with the pull request to ensure every comment is evaluated against the current code diff.