resolve-pr

Resolve GitHub pull requests by clearing blocking review threads and rechecking CI checks.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/agorokh/applied-ai-research --skill resolve-pr-agorokh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-pr
Source: https://github.com/agorokh/applied-ai-research/tree/main/.cursor/skills/resolve-pr
Command: npx skills add https://github.com/agorokh/applied-ai-research --skill resolve-pr-agorokh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves a pull request by iterating on CI results and fully clearing all blocking review threads from both humans and automation, so the PR can be merged confidently.

Core Features & Use Cases

  • CI-to-fix loop: Detects failing checks, drives the remediation cycle, and re-validates on the latest commit.
  • GraphQL reviewThreads resolution: Uses GitHub GraphQL to reliably determine whether each review thread is resolved, including correct handling of blocking isResolved: false states.
  • Async bot orchestration: Triggers common bot review workflows after each push and enforces a required cooldown (sleep 600) to prevent premature polling and missed work.
  • Exit criteria and escalation: Stops only when checks are green and blocking threads are resolved, and escalates when repeated fixes or policy exceptions are detected.

Quick Start

Use the resolve-pr skill to keep polling a PR until all required CI checks are green and all blocking GraphQL review threads are resolved.

Frequently Asked Questions about resolve-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request resolution and clear blocking GitHub review threads?

Automate pull request resolution by coordinating CI remediation and using GraphQL reviewThreads polling to clear blocking threads from humans and bots. This drives the CI-to-fix loop until all required checks are green and blocking threads are resolved for a confident merge.

What is the best way to handle async bot review workflows after pushing to a pull request?

Handle async bot review workflows after a push by triggering common bot review processes and enforcing a post-push cooldown. A required sleep 600 delay prevents premature polling, ensuring bot activity is watermarked per SHA and missed work is avoided.

How does GraphQL reviewThreads polling determine if a GitHub PR is ready to merge?

GraphQL reviewThreads polling reliably determines PR merge readiness by checking the isResolved state of each thread. It correctly identifies blocking unresolved threads from both human reviewers and automated bots, ensuring strict machine-checkable exit criteria are met before merging.

Does this approach work with enterprise GitHub draft PRs and automated code review bots?

Yes, this approach applies to enterprise GitHub workflows where bots create reviewThreads. It handles draft PR readiness evaluation and manages post-push bot triggers, coordinating CI checks and blocking thread clearance for both human and automated reviewers.

Why does my CI-to-fix loop fail to clear blocking review threads after a new push?

A CI-to-fix loop fails when post-push cooldowns are skipped. Enforcing a sleep 600 delay after pushes ensures bot review workflows complete and new bot activity is watermarked per SHA, preventing premature polling that misses unresolved blocking threads.

When should I escalate pull request resolution instead of continuing CI remediation?

Escalate pull request resolution when repeated fixes fail to turn CI checks green or when policy exceptions are detected. The process stops only when machine-checkable exit criteria confirm checks are green and all blocking GraphQL review threads are fully resolved.