explain-review

Fetches GitHub PR review comments and explains each with recommendations and learning takeaways.

Updated Dec 25, 2021
One-click install
npx skills add https://github.com/kotahashihama/dotfiles --skill explain-review-kotahashihama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain-review
Source: https://github.com/kotahashihama/dotfiles/tree/main/home/.claude/skills/explain-review
Command: npx skills add https://github.com/kotahashihama/dotfiles --skill explain-review-kotahashihama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Review comments on pull requests are often written in the reviewer's own vocabulary and assumptions, making it hard to judge what is actually being flagged and whether to act on it. This Skill retrieves unresolved review comments from a GitHub PR and breaks each one down into the intent, the current code, a proposed change, its impact, and a recommendation, so you can decide how to respond without guesswork. ## Core Features & Use Cases - Comment retrieval and filtering: Collects inline comments, review bodies, and PR conversation comments via the GitHub CLI, excluding command-only comments and already-resolved threads, with optional filtering by comment ID or criteria. - Human vs bot classification: Distinguishes commenters via the GitHub user type so follow-up work routes to the correct resolution workflow (/resolve-human-reviews or /resolve-ai-reviews). - Explanation with learning takeaways: For each comment, explains the underlying principle, checks whether the same issue appears elsewhere in the diff, and gives cues for spotting it yourself next time. - Use Case: You open a PR and find eight review comments from teammates and bots. Run this Skill to get a summary table plus detailed explanations of the non-trivial items, each with a recommendation, so you can decide what to fix before handing off to a resolution skill. ## Quick Start Ask the assistant to explain the review comments on the current pull request, optionally passing a PR number or a specific comment ID to narrow the scope.

Frequently Asked Questions about explain-review

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

FAQPage Schema
How do I explain review comments on a GitHub pull request?

Invoke the Skill with a PR number or URL, or omit arguments to target the PR linked to the current branch. It fetches unresolved comments via the GitHub CLI and explains each one with intent, current code, proposed change, impact, and a recommendation.

How to filter PR review comments to a single comment?

Pass the comment ID as an additional argument after the PR number or URL. You can also filter by criteria such as human-only comments or specific tags like [must], and pasting a comment body directly skips retrieval entirely.

Does this Skill fix code or reply to reviewers on GitHub?

No. It only explains comments and provides recommendations. Code changes are delegated to /resolve-human-reviews or /resolve-ai-reviews after you approve, and it never posts replies or resolves threads on GitHub.

How does it distinguish human reviewers from bots?

It classifies commenters mechanically using the GitHub API user.type field, where Bot indicates an automated account. It deliberately avoids judging by writing style to prevent accidentally replying to human reviewers.

What happens when a PR has many review comments?

When there are more than five comments, it first outputs a summary table with comment ID, author type, location, summary, and recommendation. Only ambiguous or heavyweight items receive detailed individual explanations, keeping the original chronological order.

Why does the Skill re-read the code before explaining a comment?

Review comments reference file and line positions that shift after new pushes, so the flagged issue may already be fixed. It always reads the current code to verify the comment still applies before presenting an explanation.