gh-address-comments

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/gh-address-comments/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

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

The content is a concise, well-structured overview that leverages a real bundled script for comment fetching. Its weaknesses are the vague 'apply fixes' step and the absence of validation/verification checkpoints around the destructive fix-application step.

Suggestions

Replace 'Apply fixes for the selected comments' with concrete, executable guidance (e.g. specific gh commands or edit steps) to raise actionability.

Add an explicit validation checkpoint after applying fixes (e.g. re-run tests / `gh pr checks` / show the user a diff for approval before pushing) to lift workflow clarity above the cap.

Reference the bundled script with a clearer path signal (e.g. 'See scripts/fetch_comments.py') and mention the github.png/svg assets only if relevant, to tighten progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is short and assumes Claude's knowledge, with only minor over-explanation (e.g. the parenthetical 'include workflow/repo scopes' and 'for example, run gh auth login once'); it is efficient with a little trimming possible, matching 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It points to an executable script ("Run scripts/fetch_comments.py") and concrete gh commands, but step 3 'Apply fixes for the selected comments' is a vague high-level hint with no specific steps, matching 'some concrete guidance but incomplete'.	3 / 5
Workflow Clarity	The three-step sequence is clear, but applying code fixes is a batch/destructive operation with no validation or verification checkpoint before/after, and the rubric caps such workflows at 3; it fits 'steps listed but validation gaps'.	3 / 5
Progressive Disclosure	The body is a lean overview that delegates the heavy lifting to a real one-level-deep reference (scripts/fetch_comments.py, which exists), with well-organized numbered sections; only minor signaling gaps keep it from 5.	4 / 5
	Total	14 / 20 Passed

Description

62%Weight 40%Scale 1-5

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

The description is specific and distinct, clearly stating what the skill does around PR comment handling and auth verification. Its main weakness is the missing explicit 'when to use' trigger guidance, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to address or fix review comments on the open PR for the current branch.'

Include a few natural synonyms/triggers like 'PR review feedback', 'resolve review threads', or 'respond to reviewer comments' to broaden natural phrasing.

Clarify how fixes get applied (e.g. 'edit code in the repo') to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	"find the open PR for the current branch", "address its comments", "verify gh auth first", and "prompt the user to authenticate" name several concrete actions with only minor gaps (no mention of how fixes are applied), landing between the 3 and 5 anchors but closer to 'several specific actions'.	4 / 5
Completeness	It gives a clear 'what' (address PR comments with gh CLI, verify auth) but has no explicit 'when should Claude use it' / 'Use when...' clause; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	"review/issue comments", "GitHub PR", "gh CLI", and "authenticate" are natural, relevant terms; the phrasing lacks synonym breadth and the 'when to use' phrasing, so it sits at 'good coverage with a few natural terms missing' rather than 5.	4 / 5
Distinctiveness Conflict Risk	The 'open GitHub PR for the current branch using gh CLI' niche is fairly specific with minor overlap risk against general git/gh skills, fitting 'mostly distinct; minor overlap with closely related skills'.	4 / 5
	Total	15 / 20 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/gh-address-comments/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.