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.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2.6k
- Forks
- 818
01 前言 Front Matter
- name
- address-pr-comments
- description
- 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.
- argument-hint
- Optionally specify a reviewer name or file to focus on
02 资源文件 13
- 参考文档architecture-decision-template.md337 B
- 资产文件data/domain-complexity.csv2.1 KB
- 资产文件data/project-types.csv758 B
- 参考文档steps/step-01-init.md6.4 KB
- 参考文档steps/step-01b-continue.md6.1 KB
- 参考文档steps/step-02-context.md8.4 KB
- 参考文档steps/step-03-starter.md11.7 KB
- 参考文档steps/step-04-decisions.md10.0 KB
- 参考文档steps/step-05-patterns.md10.7 KB
- 参考文档steps/step-06-structure.md10.9 KB
- 参考文档steps/step-07-validation.md11.4 KB
- 参考文档steps/step-08-complete.md3.1 KB
- 参考文档workflow.md1.5 KB
03 SKILL.md 正文
Address PR Review Comments
Read the active pull request, identify unresolved review comments and feedback, implement the requested changes, and resolve the threads.
When to Use
- A reviewer has left comments or change requests on the active PR
- You need to systematically work through all open review threads
- You want to respond to or implement reviewer feedback
Procedure
1. Read the Active PR
Call the github-pull-request_currentActivePullRequest tool.
Refresh logic: Check whether a refresh is needed before reading:
- Call the tool once without
refreshto get the cached state - Inspect the
lastUpdatedAtfield in the result - If the timestamp is less than 3 minutes ago, the PR is actively changing - call the tool again with
refresh: trueto ensure you have the latest comments and state - If the timestamp is older than 3 minutes, proceed with the cached data
2. Identify Unresolved Comments
From the tool result, collect all feedback that needs action:
reviewThreadsarray: inline review thread objects with anid,isResolvedflag,canResolveflag,filepath, and nestedcomments. Focus on threads whereisResolvedisfalse.timelineCommentsarray: general PR comments and reviews wherecommentTypeis"CHANGES_REQUESTED"or"COMMENTED"
Group related threads by file (file field) to handle them efficiently.
3. Plan Changes
Before modifying any files:
- Read each unresolved comment carefully
- Identify the file and location each comment refers to
- Determine the minimal correct fix for each, if a fix is needed (not all comments are worthy of a change)
- Note dependencies between comments (e.g., a rename that affects multiple files)
4. Implement Changes
Work through the grouped comments file by file:
- Read the relevant file section before editing
- Apply the requested change
- Do not refactor or modify code outside the scope of each comment
- If a comment is unclear or contradictory, note it for a follow-up reply rather than guessing
5. Verify
After all changes are made:
- Review that each originally unresolved thread has a corresponding code change or a note about why no code change was needed.
- Ensure no unrelated code was modified
6. Resolve Threads
For each thread that was addressed (either by a code change or by a deliberate decision not to change):
- Call
github-pull-request_resolveReviewThreadwith theidfrom thereviewThreadsarray. - Only resolve threads where
canResolveistrue. - Skip threads that are already resolved (
isResolved: true) or wherecanResolveisfalse.
7. Summarize
Provide a concise summary of:
- Which comments were addressed and what changes were made
- Any comments that were intentionally skipped (with reasoning)
- Any follow-up questions for the reviewer
04 同仓库更多 Skills
summarize-github-issue-pr-notification
Summarizes the content of a GitHub issue, pull request (PR), or notification, providing a concise overview of the main points and key details. ALWAYS use the skill when asked to summarize an issue, PR, or notification.
suggest-fix-issue
Given the details of an issue, suggests a fix for the issue.
show-github-search-result
Summarizes the results of a GitHub search query in a human friendly markdown table that is easy to read and understand. ALWAYS use this skill when displaying the results of a GitHub search query.
form-github-search-query
Forms a GitHub search query based on a natural language query and the type of search (issue or PR). This skill helps users create effective search queries to find relevant issues or pull requests on GitHub.
create-pull-request
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository.
write-changelog
Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.