address-pr-comments

Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

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

The content is a tight, well-sequenced procedure with concrete tool/field references, explicit validation and resolution checkpoints, and clean sectioning. It scores at the top of every dimension with no padding or concept over-explanation.

Dimension	Reasoning	Score
Conciseness	The body is lean and procedural with no re-explanation of concepts Claude already knows; every step earns its place with short, directive bullets.	3 / 3
Actionability	Names exact tools and fields (github-pull-request_currentActivePullRequest, reviewThreads, timelineComments, isResolved, canResolve, github-pull-request_resolveReviewThread) and a concrete refresh rule, giving fully actionable guidance despite being instruction-only.	3 / 3
Workflow Clarity	A clearly numbered 1-7 sequence with an explicit 'Verify' checkpoint (step 5), resolve guards (canResolve/isResolved checks), and a deliberate fallback for unclear comments.	3 / 3
Progressive Disclosure	Self-contained skill with well-organized sections (When to Use, Procedure) and no bundle files; no nested references are needed, so the well-organized single-file structure earns the top anchor.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 description: concrete capabilities, an explicit 'Use when' trigger list, a distinct PR-review niche, and correct third-person voice. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Address review comments", "resolving PR threads", "implementing requested changes from reviewers") rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' (address review comments on the active PR) and 'when' via a clearly labeled 'Use when:' trigger list, satisfying the top anchor.	3 / 3
Trigger Term Quality	The 'Use when' clause packs natural phrasings a user would actually say ('responding to PR feedback', 'fixing review comments', 'addressing code review', 'fixing PR issues'), giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to PR review comments with distinct triggers, unlikely to fire for unrelated skills; uses third person ('Address review comments') with no voice penalty.	3 / 3
	Total	12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: microsoft/vscode-pull-request-github
Path: src/lm/skills/address-pr-comments/SKILL.md
Commit: e12cbb6

Reviewed: about 10 hours 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.