code-review

Review GitHub pull requests for bugs, security issues, and correctness regressions.

6.2k|952|Updated Sep 25, 2023
One-click install
npx skills add https://github.com/microsoft/aspire --skill code-review-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/microsoft/aspire --skill code-review-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly assess a pull request for real issues like bugs, security risks, correctness regressions, and missing error handling—without focusing on style nitpicks.

Core Features & Use Cases

  • Problem-focused PR reviews: Identifies high-confidence issues (bugs, security, correctness, performance, concurrency, resource leaks).
  • PR-context guided analysis: Enforces local checkout first, then gathers diff, changed files, and existing review comments to avoid duplicates.
  • Change-area categorization: Reviews different parts of the codebase with targeted conventions (hosting, dashboard, CLI, tests, build/infra, docs/config).

Quick Start

Ask the agent to review pull request 7890 in microsoft/aspire and report only concrete problems found in the changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I find real bugs and security issues in a GitHub pull request?

To find real bugs and security issues in a GitHub pull request, review the PR diff to identify high-confidence problems like correctness regressions, concurrency leaks, and missing boundary error handling without focusing on style nitpicks.

What is the best way to triage a pull request for correctness and performance regressions?

The best way to triage a pull request for correctness and performance regressions is to categorize changed files by code area and inspect diffs against repository conventions, generating numbered, triage-ready issues for concrete problems.

How do I check a pull request for concurrency or resource leaks before merging?

To check a pull request for concurrency or resource leaks before merging, inspect the proposed changes by applying local checkout first, then gather the PR diff and changed files to report targeted findings.

Does this code review process require local checkout before inspecting the PR diff?

Yes, the code review process requires local checkout before diff inspection to gather PR context, discover changed files via GitHub tooling, and avoid duplicating existing review comments.

Can I automate pull request reviews to catch missing boundary error handling?

You can automate pull request reviews to catch missing boundary error handling by applying targeted conventions to different code areas like hosting, CLI, tests, and build infrastructure to report concrete problems.

Why does the pull request review skip style commentary and focus on bugs?

The pull request review skips style commentary to focus exclusively on high-confidence bugs, security risks, and performance concerns, ensuring developers receive triage-ready issues rather than stylistic nitpicks.