Fetch Unresolved GitHub Comments FAQs

Question 1

How does this skill handle outdated comments?

Accepted Answer

It utilizes GitHub's GraphQL API to check the status of review threads, allowing it to specifically target unresolved threads while ignoring comments that no longer apply to the current code diff.

Question 2

Can I run this skill in a CI/CD pipeline?

Accepted Answer

Yes. By setting the PR_NUMBER and GITHUB_REPOSITORY environment variables, the skill can programmatically fetch comments without needing to manually parse local git state.

Question 3

What authentication is required to use this skill?

Accepted Answer

The skill requires a GitHub personal access token or authentication via the GitHub CLI ('gh auth token'). It can read tokens from GITHUB_TOKEN or GH_TOKEN environment variables.

Question 4

Does it support private GitHub repositories?

Accepted Answer

Yes, as long as the provided GitHub token has the necessary scopes (repo) to access the private repository's pull request data.

Question 5

What format does the skill provide the data in?

Accepted Answer

The skill outputs data in a structured JSON format, which includes a total count and a 'by_file' object containing thread IDs, line numbers, diff hunks, and comment metadata.

Fetch Unresolved GitHub Comments

Key Features

Use Cases

Fetch Unresolved GitHub Comments

Key Features

Use Cases