Review Vcpkg Pr Agent Skill
Review a microsoft/vcpkg pull request end-to-end.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/microsoft/vcpkg --skill review-vcpkg-prThe instruction itself
4 sections, as written by the authorInputs
| Input | Required | Meaning |
|---|---|---|
| pr | Yes | Pull request number to review. Substituted for {{PR_NUMBER}} throughout this skill and the shared guide. |
| investigation-root | No | Directory for large temporary artifacts such as worktrees, sources, builds, examples, and installs. Final deliverables still go under reviews/ in the caller's current directory. If omitted, infer a short same-drive path when clear; otherwise ask. Never use the Copilot session directory or an arbitrary long temp path. |
| review-depth | No | One of no-examples, examples, or examples-and-patches. Default to no-examples. |
Example invocations
/review-vcpkg-pr 12345/review-vcpkg-pr 12345 investigation-root D:/vcpkg-prs
Review requirements
Read all of .github/skills/shared/review-vcpkg-pr-guide.md before reviewing; every instruction in it is mandatory.
Review the PR in a detached worktree or equivalent detached-HEAD workspace, with vcpkg.exe (Windows) or vcpkg (non-Windows) copied into it. For example, after git worktree add D:\vcpkg2 origin/master, copy .\vcpkg.exe to D:\vcpkg2. Do not switch branches or run mutable review steps in the caller's current working tree.
Required outputs
Write all final deliverables under reviews/pr-{{PR_NUMBER}} in the caller's current directory, not under investigation-root. The shared guide defines their contents.
reviews/pr-{{PR_NUMBER}}/report.mdreviews/pr-{{PR_NUMBER}}/patches/*.patch— only expected if review-depth isexamples-and-patchesand patches were produced
Do not stop until reviews/pr-{{PR_NUMBER}}/report.md exists and is complete.
Other skills for the same job
different authors, same section of the catalogue
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Comprehensive GitHub code review with AI-powered swarm coordination
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
How to use it
Take microsoft/review-vcpkg-pr from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.