address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill address-github-comments69
Quality
57%
Does it follow best practices?
Impact
88%
1.20xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/address-github-comments/SKILL.mdQuality
Discovery
57%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 has a clear niche and good 'when' guidance but lacks specificity about what concrete actions it enables. It tells Claude when to use it but not what capabilities it provides beyond vaguely 'addressing' comments. The trigger terms are adequate but could include more natural user language variations.
Suggestions
Add specific concrete actions like 'reply to review comments, resolve comment threads, add reactions, request re-review'
Include natural trigger term variations users might say: 'PR feedback', 'code review comments', 'reviewer asked', 'respond to reviewer'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub PR comments) and implies actions (address review/issue comments), but doesn't list specific concrete actions like 'reply to comments', 'resolve threads', 'request changes'. | 2 / 3 |
Completeness | Has a 'Use when' clause which addresses the 'when', but the 'what' is weak - it says 'address' comments but doesn't explain what specific actions or capabilities are available. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'review comments', 'issue comments', 'Pull Request', 'GitHub', 'gh CLI', but missing common variations users might say like 'PR feedback', 'code review', 'respond to reviewer'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focusing specifically on PR/issue comments via gh CLI - distinct from general GitHub skills, code review skills, or issue creation skills. The combination of 'comments' + 'open PR' + 'gh CLI' creates a specific trigger profile. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for addressing GitHub PR comments but falls short on actionability in the critical 'Apply Fixes' step, which is left entirely abstract. The workflow structure is present but lacks validation checkpoints to ensure comments are properly addressed. The skill would benefit from more concrete examples and explicit verification steps.
Suggestions
Expand step 3 'Apply Fixes' with concrete guidance or examples of how to systematically apply code changes based on comment feedback
Add a validation step after responding to comments to verify the response was posted (e.g., re-running gh pr view --comments to confirm)
Remove or condense the 'When to Use' section as it adds no actionable information beyond restating the overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary sections like 'When to Use' which adds no value, and 'Common Mistakes' could be tighter. The prerequisites section explaining auth is reasonable but slightly verbose. | 2 / 3 |
Actionability | Provides some concrete commands (gh pr view, gh pr comment) but step 3 'Apply Fixes' is vague with no actual code or specific guidance. The workflow describes what to do conceptually rather than providing executable steps for the core task. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. No verification that fixes actually address the comments, no feedback loop for checking if responses were posted successfully, and step 3 is too abstract to follow. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~50 lines), the structure is appropriate with clear sections. No unnecessary nesting or references to external files. Content is well-organized with logical flow from prerequisites to workflow to common mistakes. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.