address-github-comments

Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, single-purpose skill with executable gh commands, weakened by boilerplate filler sections, incomplete guidance in the apply-fixes step, and a missing verification checkpoint before responding to threads.

Suggestions

Add an explicit verification step before responding to comments (e.g., run tests or confirm the diff compiles) so the workflow has a validation feedback loop.

Replace the abstract 'Apply Fixes' step with concrete guidance, and remove the hardcoded reply body in favor of instructing Claude to summarize what was changed per thread.

Cut the tautological 'When to Use' sentence and the generic 'Limitations' boilerplate so every section earns its tokens.

Dimension	Reasoning	Score
Conciseness	The core Overview/Workflow/Common Mistakes sections are lean and assume Claude's competence, but the tautological 'When to Use' ("applicable to execute the workflow or actions described in the overview") and generic 'Limitations' boilerplate add explanation that does not earn its tokens, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the fully lean anchor 3.	2 / 3
Actionability	It provides executable commands ("gh auth status", "gh pr view --comments", "gh pr comment <PR_NUMBER> --body ..."), but step 3 'Apply Fixes' is abstract, step 1 offers a vague 'custom script if available,' and the reply uses a hardcoded generic body, matching the 'some concrete guidance but incomplete' anchor; it is not 3 because key steps lack copy-paste-ready specifics.	2 / 3
Workflow Clarity	A clear 4-step sequence with a user-confirmation checkpoint is present, but batch addressing of comments that modifies code has no verification/validation feedback loop (e.g., confirming fixes compile or tests pass before responding), which per the scoring notes caps workflow_clarity at 2; it is not 1 because the sequence is explicit and ordered.	2 / 3
Progressive Disclosure	This is a short single-purpose skill under 50 lines with no bundle files, and its content is well-organized into clear sections, which per the simple-skills scoring note qualifies for anchor 3 even without external file references; it is not 2 because no content is inappropriately inlined or nested.	3 / 3
	Total	9 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description with an explicit 'Use when' trigger and a well-scoped niche, though the action language is abstract and natural-keyword coverage is partial.

Dimension	Reasoning	Score
Specificity	It names the domain ("review or issue comments on an open GitHub Pull Request") and the tool ("using the gh CLI") but only the abstract action "address," with no enumeration of concrete capabilities; this matches the 'names domain and some actions, but not comprehensive' anchor and falls short of the multiple-specific-actions anchor 3.	2 / 3
Completeness	It answers both 'what' (address PR/issue comments via gh) and 'when' with an explicit trigger clause ("Use when you need to address..."), matching the 'clearly answers both what AND when with explicit triggers' anchor; it is not 2 because the when-trigger is explicit, not merely implied.	3 / 3
Trigger Term Quality	Natural terms like "review or issue comments" and "GitHub Pull Request" appear, but common variations a user would say (e.g., "PR comments," "reply to reviewers," "resolve threads") are missing, matching the 'some relevant keywords but missing common variations' anchor rather than full coverage at 3.	2 / 3
Distinctiveness Conflict Risk	The scope is tightly confined to GitHub PR/issue comments via the gh CLI, a clear niche with distinct triggers unlikely to conflict with other skills, matching anchor 3; it is not 2 because it is not merely 'somewhat specific' but precisely scoped.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.