Review and triage PR review comments for the current branch using gh CLI. Fetches review comments, groups them into threads, separates human from bot feedback, and walks through each unresolved comment interactively. Use when the user asks to check PR comments, review feedback, address review comments, or triage PR reviews.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities (fetching, grouping, separating, and interactively walking through PR comments) and provides explicit trigger guidance via a 'Use when' clause with multiple natural trigger terms. It is well-scoped to a distinct niche (PR review comment triage via gh CLI) with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fetches review comments, groups them into threads, separates human from bot feedback, and walks through each unresolved comment interactively. These are clear, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (review and triage PR review comments, fetch, group, separate, walk through interactively) and 'when' (explicit 'Use when' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'PR comments', 'review feedback', 'address review comments', 'triage PR reviews', 'gh CLI', 'current branch'. Good coverage of natural variations a user might use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: PR review comment triage using gh CLI on the current branch. The combination of PR reviews, gh CLI, threading, and interactive walkthrough makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with a well-sequenced multi-step workflow and concrete, executable gh CLI commands throughout. The interactive triage pattern (present → propose → ask → execute) is well-designed. Minor weaknesses include some over-explanation of concepts Claude already understands and the monolithic structure that could benefit from splitting detailed API reference into a supporting file.
Suggestions
Trim explanatory text in Steps 3-4 (e.g., Claude doesn't need to be told what in_reply_to_id means or how to identify bot accounts) to improve conciseness.
Consider extracting the gh API command reference into a separate COMMANDS.md file, keeping SKILL.md as a workflow overview with inline references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete commands and structured steps, but includes some unnecessary explanation (e.g., explaining what 'in_reply_to_id: null' means, describing what bot comments are). The thread-tracking details in Step 3 could be trimmed since Claude understands data grouping. | 2 / 3 |
Actionability | Provides fully executable gh CLI commands with specific --jq filters, concrete API endpoints for posting replies, clear option menus for user interaction, and specific tool references (TodoWrite, AskQuestion). Commands are copy-paste ready with appropriate placeholders. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with guard conditions (Step 1 branch check, PR not found), explicit decision points (Step 5 options), separation of concerns (fetch → organize → classify → present → execute → summarize), and a feedback loop where fixes are shown as diffs before committing. The summary table at the end serves as a verification checkpoint. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical flow, but it's a fairly long single file with no references to supporting files. The edge cases section is appropriately brief, but the detailed API commands and thread-grouping logic could potentially be split out for a cleaner overview. For a skill of this complexity, some external references would improve navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
0f36ad4
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.