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:duclm1x1/Dive-Ai --skill address-github-comments78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 good trigger terms and a clear niche for PR comment handling, but lacks specificity about what concrete actions it can perform. It tells Claude when to use it but not comprehensively what it can do beyond vaguely 'addressing' comments.
Suggestions
Add specific concrete actions like 'reply to review comments, resolve comment threads, respond to requested changes, mark conversations as resolved'
Expand the 'what' portion before the 'Use when' clause to list 2-4 specific capabilities the skill provides
| 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', 'mark as resolved', etc. | 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 natural keywords users would say: 'review comments', 'issue comments', 'Pull Request', 'GitHub', 'PR', 'gh CLI'. These are terms users naturally use when discussing PR feedback. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on PR/issue comments via gh CLI. Distinct from general GitHub skills, code review skills, or PR creation skills due to the specific focus on addressing existing comments. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%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 PR comments with good conciseness and structure. However, it falls short on actionability in the critical 'Apply Fixes' step and lacks validation checkpoints to ensure fixes are correct before marking comments as resolved.
Suggestions
Add concrete guidance for the 'Apply Fixes' step - either example code patterns or specific instructions on how to locate and modify the relevant code based on comment context
Add a validation step between applying fixes and responding to comments (e.g., run tests, verify the change addresses the specific feedback)
Include an example of categorizing comments (e.g., 'bug fix', 'style change', 'clarification needed') with a sample plan output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding unnecessary explanations of what GitHub PRs or comments are. Every section serves a purpose and assumes Claude's competence with basic concepts. | 3 / 3 |
Actionability | Provides some concrete commands (gh pr view, gh pr comment) but 'Apply Fixes' step is vague with no executable guidance. The categorization step lacks concrete examples of how to structure the plan. | 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 testing changes before responding, and no guidance on handling failed fixes. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~40 lines), the structure is appropriate with clear sections. No need for external references given the scope, and content is well-organized with logical flow. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.