github

Fetch unresolved GitHub PR review comments via gh CLI and GraphQL.

3|Updated Jul 13, 2020
One-click install
npx skills add https://github.com/nieomylnieja/dotfiles --skill github-nieomylnieja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/nieomylnieja/dotfiles/tree/main/config/agents/skills/github-pr-comments
Command: npx skills add https://github.com/nieomylnieja/dotfiles --skill github-nieomylnieja

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Addressing GitHub PR comments can be tedious when there are many unresolved threads. This skill helps you focus on unresolved feedback and respond efficiently.

Core Features & Use Cases

  • Get Unresolved Comments: Fetch unresolved review threads for the current PR.
  • Structured Output: Return path, line, body, and isOutdated for easy triage.
  • Guided Resolution: Provide a recommended reply and leave threads unresolved for manual review.

Quick Start

Run the get-unresolved-comments.sh script to fetch unresolved review comments for the current PR.

Frequently Asked Questions about github

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

FAQPage Schema
How do I fetch unresolved GitHub PR review comments for the current branch?

Fetch unresolved GitHub PR review comments by running a script that uses the gh CLI and GraphQL to detect the current repo and branch, querying pending threads and returning path, line, body, and isOutdated status.

What's the best way to triage pending pull request feedback during code review?

Triage pending pull request feedback by fetching unresolved review threads directly from the repository context, which outputs structured path, line, and body details for quick decision making during code review workflows.

Do I need gh CLI and jq installed to retrieve unresolved PR threads?

Yes, you need gh CLI and jq installed to retrieve unresolved PR threads, as the script relies on gh for GraphQL queries against GitHub and jq for processing the structured JSON output.

Can I automate GitHub PR comment triage for downstream automation pipelines?

Automate GitHub PR comment triage by running the script to output unresolved thread data in a compact format suitable for downstream automation, providing recommended replies while leaving threads unresolved for manual review.

Does this script detect the repository and branch automatically for GitHub PR comment retrieval?

Yes, the script detects the current repository and branch automatically, querying unresolved GitHub PR review threads via GraphQL without requiring manual repo or branch input.

How does the script handle outdated comments when fetching unresolved PR threads?

The script handles outdated comments by including an isOutdated flag in the structured output, allowing you to filter or skip outdated unresolved threads when triaging GitHub PR review feedback.