comment-commentary

Analyzes GitHub pull-request review threads one at a time with evidence-based recommendations.

Updated Feb 26, 2025
One-click install
npx skills add https://github.com/adschill/dev-config --skill comment-commentary-adschill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comment-commentary
Source: https://github.com/adschill/dev-config/tree/main/skills/comment-commentary
Command: npx skills add https://github.com/adschill/dev-config --skill comment-commentary-adschill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working through a backlog of inline GitHub PR review comments is tedious and error-prone: reviewers' requests get lost, already-addressed threads waste time, and it is hard to judge whether a suggestion is sound without digging into the diff and surrounding code. This Skill triages unresolved review threads one at a time, gathers the relevant evidence, and gives a pragmatic assessment of what the reviewer wants and what to do about it. ## Core Features & Use Cases - Thread-by-thread triage: Fetches all unresolved review threads via the GitHub GraphQL API, classifies each as actionable or already handled, and presents the oldest actionable thread first. - Evidence-grounded analysis: Reads the full thread, the cited diff hunk, the current PR diff, and local code (committed, staged, and unstaged changes) before judging the reviewer's request. - Pragmatic recommendations: States when a comment is stale, already addressed, incorrect, or over-scoped, and recommends the smallest correct change with a concrete next step. - Use Case: After pushing updates to a PR, ask for the next unresolved comment; the Skill skips threads already remedied by your local changes and analyzes the oldest remaining one, including a file reference and implementation direction. ## Quick Start Use the comment-commentary skill to analyze the next unresolved review thread on my current pull request.

Frequently Asked Questions about comment-commentary

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

FAQPage Schema
How do I find the next unresolved review comment on a GitHub PR?▼

Invoke the skill on the current checkout; it discovers the PR with gh pr view, fetches review threads via the GitHub GraphQL API, filters out resolved or already-handled threads, and selects the oldest actionable one for analysis.

How to analyze a specific GitHub discussion URL from a pull request?▼

Paste the discussion URL matching github.com/<owner>/<repo>/pull/<number>#discussion_r<id>. The skill fetches that single comment thread via the pulls/comments API and analyzes it directly, bypassing the unresolved-thread queue.

Does this skill automatically reply to or resolve GitHub review threads?▼

No. The skill is analysis-only: it never edits code, posts replies, resolves threads, or runs mutating commands. It recommends a change and waits for an explicit implementation request before any code work begins.

Can it tell if a review comment is already fixed in my local changes?▼

Yes. When the local checkout matches the PR, it inspects the committed PR diff plus staged and unstaged diffs to determine whether the requested outcome is already remedied, and skips those threads unless the relationship is ambiguous.

What happens when there are no unresolved PR comments left?▼

The skill states plainly that no actionable threads remain. It caches the thread queue in conversation, so follow-up requests like "next comment" reuse the cache without re-querying GitHub unless review activity or relevant files changed.