Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/fetch-unresolved-comments
Fetch unresolved PR review comments using GitHub GraphQL API, filtering out resolved and outdated feedback.
Passed 14 of 18 test cases with the skill, and 9 of 18 without it.
and 5 more in the full report
8 fixed9 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What top-level JSON key indicates the aggregate number of open comments in the script's output?
| Checked | Without skill | With skill |
|---|---|---|
| Expects the JSON output key total | Missed | Passed |
The instructions your model reads when the skill loads.
Uses GitHub's GraphQL API to fetch only unresolved review thread comments from a pull request.
Parse PR information:
PR_NUMBER and GITHUB_REPOSITORY are set, read them and parse GITHUB_REPOSITORY as owner/repo and use PR_NUMBER directlygh pr view --json url -q '.url' to get the current branch's PR URL and parse to extract owner, repo, and PR numberRun the Python script:
GITHUB_TOKEN=$(gh auth token) \
uv run python .claude/skills/fetch-unresolved-comments/fetch_unresolved_comments.py <owner> <repo> <pr_number>
Script options:
--token <token>: Provide token explicitly (default: GITHUB_TOKEN or GH_TOKEN env var)Parse the JSON output: The script always outputs JSON with:
total: Total number of unresolved comments across all threadsby_file: Review threads grouped by file path (each thread contains multiple comments in a conversation){
"total": 3,
"by_file": {
test cases passed, vs 9 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.