review-vcpkg-pr
Review a microsoft/vcpkg pull request end-to-end.
- License 许可
- MIT
- 所属仓库
- microsoft/vcpkg
- 最近更新
- 2026-11-14
- Stars
- ★ 2.8w
- Forks
- 7.8k
01 前言 Front Matter
- name
- review-vcpkg-pr
- description
- Review a microsoft/vcpkg pull request end-to-end.
- disable-model-invocation
- true
03 SKILL.md 正文
Inputs
| 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 workspaces and intermediate artifacts: sources, builds, installs, logs, and examples. 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
Before changing directories, resolve investigation-root and reviews/pr-{{PR_NUMBER}} against the caller's original directory to absolute paths. Use the resolved report directory as {{REPORT_DIR}} throughout this skill and the shared guide; never rebase it onto the review workspace.
Before leaving the caller's directory, read all of .github/skills/shared/review-vcpkg-pr-guide.md; every instruction in it is mandatory.
Review the PR in a detached worktree or equivalent detached-HEAD workspace. Copy the caller's vcpkg.exe (Windows) or vcpkg (non-Windows) into its root. Do not switch branches or run mutable review steps in the caller's working tree.
If VCPKG_DOWNLOADS is already nonempty, preserve it for all review commands and subagents. Use that shared directory only through vcpkg; never clean or delete it. Otherwise, do not set it.
Required outputs
Write only final deliverables in {{REPORT_DIR}}, not under investigation-root. The shared guide defines their contents:
report.md, including the guide's self-contained## Fix handofffor use without this session's chat history.patches/*.patch-- only forexamples-and-patches; omit if no patches were produced and explain any unpatched issues in the report.
Do not stop until report.md exists in {{REPORT_DIR}} and is complete.
04 同仓库更多 Skills
review-vcpkg-prs-today
Review open non-draft microsoft/vcpkg pull requests updated in the last 30 days. Use when asked for batch triage, per-PR review reports, an index grouped by verdict, or grouping competing PRs that modify the same port.
fix-reviewed-vcpkg-pr
Address findings in an existing report produced by review-vcpkg-pr or review-vcpkg-prs-today, then push fixes for the user to submit to the contributor. Use only for follow-up fixes to those reviews, including batches. Do not use for generic bug fixes, issue resolution, or PRs without an existing review report. Never open a PR.
fetch-vcpkg-ci-logs
Fetch vcpkg Azure DevOps metadata, failed-step logs, and selected artifacts. Use for acquiring CI evidence, not diagnosing or reporting regressions; use analyze-ci-failures for those tasks. Skip when supplied logs are sufficient.
evaluate-new-port
Audit a vcpkg port locally. Reads the port metadata and build recipe, installs the port, inspects extracted sources and installed files, and produces a report covering license risks, vendored code, optional dependencies, and other port review suggestions.
code-review
Review microsoft/vcpkg pull requests in GitHub Copilot code review. Check port correctness, packaging, dependencies, licenses, and consumer integration; validate examples when the review time budget permits.
analyze-ci-failures
Analyze collected vcpkg CI failure evidence, classify regressions and known failures, identify root causes, recommend actions, and generate a report by package and triplet. USE FOR: explicit requests for CI regression triage, a failure inventory, baseline classification, action recommendations, or a formal CI failure report. DO NOT USE FOR: fetching logs as the final output, targeted debugging of one failure, answering a one-off question about logs the user pasted or pointed at, general coding, creating ports, or modifying portfiles. When requested analysis lacks local evidence, run fetch-vcpkg-ci-logs as the acquisition stage first. **ANALYSIS SKILL** USES: locally collected CI logs, vcpkg baselines, Azure DevOps metadata.