skills.rest
BillChirico
BillChiricoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

manage-prs

Inspect GitHub PR review threads and CI checks to resolve blockers.

5|Updated Nov 27, 2025
Search Tags:#automation#code review#github#graphql#pull requests#ci failures#review threads
One-click install
npx skills add https://github.com/BillChirico/bills-agent-skills --skill manage-prs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-prs
Source: https://github.com/BillChirico/bills-agent-skills/tree/main/manage-prs
Command: npx skills add https://github.com/BillChirico/bills-agent-skills --skill manage-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill resolves GitHub pull request blockers by systematically inspecting review threads, requested changes, top-level PR comments, merge conflicts, and CI/CD check failures so your PR can move forward.

Core Features & Use Cases

  • End-to-end PR maintenance workflow: Re-reads live GitHub PR state, inventories every blocker, fixes root causes, and only resolves review threads after the branch is pushed and the exact live thread IDs are confirmed.
  • CI-aware verification loop: Distinguishes failing, pending, skipped, and unknown checks and ties fixes to the failing workflows rather than relying on local test results alone.
  • Use cases: Fixing CHANGES_REQUESTED review feedback, clearing unresolved review threads after making/pushing the actual code changes, and unblocking merges caused by failing required checks or merge conflicts.

Quick Start

Use manage-prs to inspect a target PR, fix review/CI blockers in the repo, push the changes, then resolve only the exact GitHub review thread IDs that were actually fixed.

Frequently Asked Questions about manage-prs

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

FAQPage Schema
How do I automatically resolve GitHub pull request review threads after pushing fixes?▼

To resolve GitHub pull request review threads, you must first push your code fixes and then target the exact live thread IDs. The manage-prs workflow re-reads live PR state via GitHub GraphQL to deterministically resolve only the threads actually addressed by your pushed changes.

What's the best way to clear CI check failures and requested changes on a pull request?▼

Clearing CI check failures and requested changes requires inspecting failing workflows and PR conversation blockers. This workflow inventories every blocker, ties fixes to failing CI checks rather than local tests, and clears CHANGES_REQUESTED feedback to prepare the PR for merge.

Do I need GitHub CLI access to manage pull request conversations and mergeability issues?▼

Yes, you need GitHub CLI access with a valid repo-scoped token to manage pull request conversations and mergeability issues. The workflow relies on the GitHub CLI and Python to execute GraphQL queries that read live PR state and resolve review threads.

How does the GitHub GraphQL API identify which unresolved review threads to clear on a PR?▼

The GitHub GraphQL API identifies unresolved review threads by re-reading the live PR state and inventorying conversation blockers. It confirms the exact live thread IDs after fixes are pushed, ensuring only threads with actual code changes applied are deterministically resolved.

Can I fix pull request merge conflicts and skipped CI checks without running local tests?▼

Yes, you can fix pull request merge conflicts and skipped CI checks without local tests. The workflow distinguishes failing, pending, skipped, and unknown CI states by tying fixes directly to live GitHub workflow check states rather than relying on local test results.

Why does a pull request stay blocked after I resolve code review comments locally?▼

A pull request stays blocked because live GitHub review threads remain unresolved on the server. You must push your fixes, verify the exact live thread IDs using GitHub GraphQL, and then explicitly resolve those threads to clear the PR conversation blockers for merging.

Related Skills

Explore More Software Engineering Skills→
tobihagemanntobihagemann
399

fetch-pr-comments

Fetch and summarize unresolved GitHub PR review comments via GraphQL.

Community
Intermediate
pacaplanpacaplan
30

flokay:wait-ci

Poll GitHub CI check and pull request review statuses for the current branch.

Community
Advanced
drillandrillan
1

merge-pr

Wait for CI checks and merge GitHub pull requests with a chosen strategy.

Community
Advanced
fairy-pittafairy-pitta

resolve-comments

Resolve addressed GitHub pull request review threads via GitHub CLI and GraphQL API.

Community
Intermediate