copilot-address-reviews

Fetches GitHub Copilot review items via gh CLI and validates them against source/tests before committing fixes.

2|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/lestrrat/claude-code --skill copilot-address-reviews
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-address-reviews
Source: https://github.com/lestrrat/claude-code/tree/main/skills/copilot-address-reviews
Command: npx skills add https://github.com/lestrrat/claude-code --skill copilot-address-reviews

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, python3, and includes scripts (resource) components.

What problem does it solve?

Evaluate and address GitHub Copilot PR review items for a GitHub pull request. Use when a user provides a GitHub PR link and wants Copilot review comments checked, verified, fixed, and summarized. Fetch review items with gh, verify each claim against source/tests before changing code, ask user before making subjective or constraint-driven changes, then work items one by one.

Core Features & Use Cases

  • Fetch and enumerate Copilot review items for a PR using the gh CLI, normalizing unresolved items for review.
  • Validate each Copilot claim against source code/tests before applying changes, ensuring traceability.
  • Apply smallest possible code change per item, commit per item, and update or close related GitHub review threads as needed.
  • Require user confirmation for subjective, design, or constraint-driven decisions; supports iterative, item-by-item processing.

Quick Start

Run the fetch script from the skill directory: ./scripts/fetch-review-items.sh <pr-url> to start collecting Copilot review items and dedup them.

Frequently Asked Questions about copilot-address-reviews

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate addressing Copilot code review comments on a GitHub PR?

Automating Copilot PR reviews involves fetching review items with the gh CLI, validating each comment against your source code and tests, and committing fixes one by one. The workflow requires user confirmation for subjective design changes before applying any code modifications.

What is the process for verifying Copilot review suggestions before changing code?

Verifying Copilot suggestions means validating every review claim against your source code and tests before editing. The workflow ensures traceability by applying the smallest possible change per item and requiring user confirmation for subjective or design-driven modifications.

Do I need the gh CLI installed to fetch and process Copilot PR review items?

Yes, the gh CLI is required to fetch GitHub pull request review data. The workflow also depends on jq and python3 to normalize unresolved review items, deduplicate them, and process the feedback data for item-by-item validation.

Can I resolve GitHub review threads automatically after committing Copilot fixes?

Yes, you can resolve GitHub review threads automatically after committing validated fixes. The workflow processes Copilot review items iteratively, applying changes per item and updating or closing the corresponding review threads on the GitHub pull request.

How do I handle subjective Copilot code review suggestions that require design decisions?

For subjective or constraint-driven Copilot suggestions, the workflow pauses and requires explicit user confirmation before making any code changes. This ensures you maintain control over design decisions while automating the validation of objective code review items.