CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gh-address-comments

Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging (use gh-fix-ci), or general Git operations.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A concise, well-structured skill body that externalizes comment-fetching to a real script and includes a clear human-in-the-loop checkpoint. Its main weakness is the absence of a validation step after applying code fixes, which caps workflow clarity at 3, and an abstract 'apply fixes' step that lacks concrete guidance.

Suggestions

Add a validation/verification step after applying fixes (e.g., run the project's test/build command, or re-check that each selected comment is actually resolved) before considering the task complete.

Make the 'Apply fixes for the selected comments' step more actionable by stating how fixes should be made (edit the relevant files, run tests per comment) rather than leaving it abstract.

Consider a final confirmation loop where the user verifies the applied fixes address the numbered comments before finishing.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines), assumes Claude's competence, and does not over-explain what a PR or gh is; almost every line is actionable instruction, with only trivial redundancy like 'to authenticate with GitHub' after `gh auth login`.

5 / 5

Actionability

Provides concrete executable commands (`gh auth status`, `gh auth login`, `scripts/fetch_comments.py`) for the mechanical steps, but the core 'Apply fixes for the selected comments' step is abstract with no concrete guidance on how fixes are applied.

4 / 5

Workflow Clarity

The numbered sequence (inspect -> ask user -> apply fixes) is clear and includes a human-in-the-loop checkpoint, but there is no validation/verification step after applying code fixes; per the batch/destructive cap, a comment-fixing workflow without validation cannot score above 3.

3 / 5

Progressive Disclosure

A short, well-organized body with one clearly signaled, one-level-deep reference to a real bundle file (scripts/fetch_comments.py); the fetching logic is appropriately externalized to that script, satisfying the under-50-line simple-skill guidance.

5 / 5

Total

17

/

20

Passed

Description

95%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.

A strong, well-targeted description that uses third-person voice, names concrete actions, and supplies explicit natural trigger phrases plus clear negative-boundary guidance. Minor specificity gap only because the fixing mechanics live in the body rather than the description.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Address review and issue comments on the open GitHub PR for the current branch using gh CLI', 'Verifies gh auth first and prompts to authenticate') plus explicit exclusions, leaving only minor gaps since the actual fixing mechanism is delegated to the body.

4 / 5

Completeness

Explicitly answers both 'what' (address PR comments via gh CLI, verify auth) and 'when' (Use when user says the listed phrases), with concrete trigger phrases and boundary guidance.

5 / 5

Trigger Term Quality

Four natural user phrases are quoted verbatim ('address PR comments', 'fix review feedback', 'respond to PR review', 'handle PR comments'), giving comprehensive synonym coverage of what a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (PR comment handling for the current branch's PR) with explicit exclusion of creating PRs, CI debugging (gh-fix-ci), and general Git operations, minimizing conflict risk.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tech-leads-club/agent-skills

Path

packages/skills-catalog/skills/(development)/gh-address-comments/SKILL.md

Reviewed

Table of Contents

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.