copilot-review

Delegate code review to the GitHub Copilot CLI across staged, branch, commit, and PR diffs.

1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/DIO0550/d-market --skill copilot-review-dio0550
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-review
Source: https://github.com/DIO0550/d-market/tree/main/plugins/code-review-plugin/skills/copilot-review
Command: npx skills add https://github.com/DIO0550/d-market --skill copilot-review-dio0550

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill delegates code review tasks to GitHub Copilot via the Copilot CLI, enabling faster, automated feedback on code changes.

Core Features & Use Cases

  • Copilot-driven code review for staged, uncommitted, file, files, branch, commit, and PR diffs.
  • Outputs structured feedback and stores results in the .copilot-reviews directory for traceability.
  • Use case: before merging, trigger a Copilot review on the current diff to surface issues and improvement opportunities.

Quick Start

Review the current changes with Copilot to obtain feedback and a summary.

Frequently Asked Questions about copilot-review

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

FAQPage Schema
How do I automate code review for git diffs using Copilot CLI?

Automated code review with Copilot CLI delegates feedback generation to GitHub Copilot for git diffs. It analyzes staged, unstaged, file, branch, commit, and PR contexts, then stores structured results in the .copilot-reviews directory for traceability.

Do I need GitHub Copilot CLI installed to automate pull request reviews?

Yes, GitHub Copilot CLI must be installed and authenticated to automate pull request reviews. The Skill delegates diff analysis directly to the Copilot CLI, requiring valid authentication to generate structured feedback and store results.

What git contexts are supported for Copilot-driven code analysis?

Copilot-driven code analysis supports staged, unstaged, file, files, branch, commit, and PR diff contexts. It processes these git changes via the Copilot CLI and outputs structured feedback stored locally for traceability.

Where are automated Copilot code review results stored?

Automated Copilot code review results are stored in the .copilot-reviews directory. This ensures traceability for feedback generated on git diffs across branch, commit, staged, and PR contexts analyzed by the Copilot CLI.

Can I trigger an automated code review before merging a git branch?

Yes, you can trigger an automated Copilot code review before merging a git branch. It delegates the branch diff to the Copilot CLI to surface issues and improvement opportunities, storing the structured feedback locally.

What is the best way to analyze uncommitted code changes with Copilot?

The best way to analyze uncommitted code changes with Copilot is delegating unstaged or staged diffs to the Copilot CLI. It generates structured feedback on the current changes and saves the results in the .copilot-reviews directory.