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:boisenoise/skills-collections --skill address-github-comments71
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
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 key steps. The workflow structure is present but lacks validation checkpoints, and some sections (Common Mistakes, When to Use) add little value while consuming tokens.
Suggestions
Make 'Apply Fixes' step actionable by providing concrete guidance or example commands for common fix patterns
Add a validation step after responding to comments (e.g., verify with 'gh pr view --comments' that responses were posted)
Remove or condense 'Common Mistakes' and 'When to Use' sections - these explain things Claude already knows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary sections like 'When to Use' which adds no value, and the 'Common Mistakes' section states obvious points Claude would already know. | 2 / 3 |
Actionability | Provides some concrete commands (gh pr view, gh pr comment) but 'Apply Fixes' step is vague with no actual code/commands, and 'Categorize and Plan' lacks executable guidance. | 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. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~50 lines), the structure is appropriate with clear sections. No need for external references given the scope, and content is well-organized. | 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.