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

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

72%

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

A concise, well-organized skill body with a clear sequence and a real single-level script reference. It is held back by the vague 'Apply fixes' step and the lack of a verification checkpoint confirming fixes took effect.

Suggestions

Make step 3 actionable: specify how fixes are applied (e.g., edit files locally, commit, and `gh pr comment`/push) instead of the bare 'Apply fixes for the selected comments'.

Add a verification checkpoint after fixes are applied, such as re-running scripts/fetch_comments.py or `gh pr checks`, to confirm comments are resolved before finishing.

Reference the bundled assets (assets/github.png, assets/github-small.svg) only if they are meant to be used, or remove them to avoid an unreferenced bundle.

Dimension	Reasoning	Score
Conciseness	The body is lean (under 20 lines), assumes Claude's competence, and avoids explaining concepts Claude already knows; every line is an actionable instruction with no padding.	3 / 3
Actionability	Concrete executable commands appear in the prereq ('gh auth login', 'gh auth status', 'sandbox_permissions=require_escalated') and step 1, but step 3 'Apply fixes for the selected comments' is abstract with no concrete guidance on how to apply fixes.	2 / 3
Workflow Clarity	Steps are clearly sequenced with an auth-verification checkpoint and a retry feedback loop, but there is no validation that applied fixes actually succeeded, which caps workflow clarity at 2 for destructive/batch-style edits.	2 / 3
Progressive Disclosure	The short body is well-organized into numbered sections and points to one real one-level-deep reference (scripts/fetch_comments.py), with no nested references, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-targeted description that names concrete actions and natural trigger terms within a distinct niche. Its main weakness is the absence of an explicit 'Use when...' clause, leaving the invocation timing implied rather than stated.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('find the open PR for the current branch', 'address its comments with gh CLI', 'verify gh auth first', 'prompt the user to authenticate'), matching the 'Lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks an explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2 with the 'when' only implied.	2 / 3
Trigger Term Quality	It uses natural terms a user would say ('review/issue comments', 'GitHub PR', 'current branch', 'gh CLI'), giving good coverage of likely phrasings rather than opaque jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific (addressing comments on the open PR for the current branch via gh CLI), making it unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: openai/skills
Commit: 49f948f

Reviewed: 18 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.