Dev10x:gh-pr-doctor

Audit merged GitHub Pull Requests for unresolved review threads and create follow-up issues.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-gh-pr-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:gh-pr-doctor
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/gh-pr-doctor
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-gh-pr-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the audit of merged Pull Requests (PRs) to identify and track unresolved review threads, preventing tech debt from accumulating.

Core Features & Use Cases

  • PR Audit: Scan merged PRs for unresolved review comment threads.
  • Grouping & Issue Creation: Group findings by theme and create follow-up issues.
  • Audit Trail: Post comments on PRs to mark them as audited.
  • Integration: Can be used standalone or integrated into maintenance workflows.

Quick Start

Run the skill to audit merged PRs in the current repository: /Dev10x:gh-pr-doctor

Frequently Asked Questions about Dev10x:gh-pr-doctor

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

FAQPage Schema
How do I audit merged GitHub Pull Requests for unresolved review threads?

You can audit merged GitHub Pull Requests by running an automated script that scans for unresolved review comment threads, groups findings by theme, and creates follow-up issues to track them. This prevents unresolved comments from accumulating as tech debt.

What is the best way to prevent tech debt from unresolved code review comments?

Preventing tech debt from unresolved code review comments involves automating a PR audit to detect lingering threads. The script groups these unresolved threads by theme and automatically opens follow-up issues for tracking.

Do I need the gh CLI to automate PR audits for unresolved threads?

Yes, you need the gh CLI because the automation requires GitHub API access to scan merged PRs, extract unresolved review threads, and post audit trail comments. Python scripts handle the execution logic.

Can I integrate unresolved review thread tracking into maintenance workflows?

You can integrate unresolved review thread tracking into maintenance workflows. The script operates standalone or within continuous integration pipelines to audit merged PRs and post audit trail comments.

How does PR audit grouping work for unresolved GitHub issues?

PR audit grouping works by scanning merged PRs for unresolved review threads and categorizing them by theme. The script then creates grouped follow-up issues on GitHub to ensure related technical debt is tracked together.

What are the limitations of automating GitHub PR audits for unresolved threads?

Limitations of automating GitHub PR audits include dependency on GitHub API access and the gh CLI. The script requires Python to execute and is specifically designed for auditing merged PRs, not open ones.