review-vcpkg-prs-today
द्वारा microsoft
पिछले 30 दिनों में अपडेट किए गए खुले गैर-ड्राफ्ट microsoft/vcpkg पुल अनुरोधों की समीक्षा करें। बैच ट्राइएज, प्रति-PR समीक्षा रिपोर्ट, या इसके द्वारा समूहीकृत सूचकांक के लिए पूछे जाने पर उपयोग करें…
npx skills add https://github.com/microsoft/vcpkg --skill review-vcpkg-prs-todayInputs
| Input | Required | Meaning |
|---|---|---|
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-prs-today investigation-root D:/vcpkg-prs/review-vcpkg-prs-today review-depth examples/review-vcpkg-prs-today investigation-root D:/vcpkg-prs and review-depth examples
Procedure
- Before changing directories, resolve
investigation-root,reviews/, and.github/skills/shared/review-vcpkg-pr-guide.mdagainst the caller's original directory to absolute paths. Keep the resolved reviews directory asreviews-root; never rebase it onto a worker's workspace. - Discover candidates using GitHub search (
gh apior the Search API), not the generic pulls list:repo:microsoft/vcpkg is:pr is:open draft:false updated:>=<today minus 30 days>. Prefer authentication viaghorGITHUB_TOKENto avoid low unauthenticated limits. - Fetch each candidate's changed files; identify ports from
ports/<portname>/. - Prepare isolated workspaces as below. Review every candidate independently with a
general-purposeworker using its default high-capability model; do not override it with a fast or lightweight model. Require it to read the entire guide and follow every instruction. Group competition only in the final index. Pass each worker:- PR number (
{{PR_NUMBER}}). - Selected
review-depth. - Absolute workspace and worker-local
investigation-root. - Absolute
{{REPORT_DIR}}(pr-{{PR_NUMBER}}underreviews-root). - Absolute guide path.
- PR number (
- Write each report when completed. Write
index.mdlast from the final per-PR results and port-specific competition groups.
Parallel execution safety
- Give each concurrent worker its own writable detached worktree or equivalent detached-HEAD workspace and intermediate artifacts under
investigation-root. Never share a writable repository path between workers. - Create all isolated workspaces before launching workers. Copy the caller's
vcpkg.exe(Windows) orvcpkg(non-Windows) into each workspace root. - Use the caller's working tree only when exactly one worker is active and the user explicitly allows it.
- If
VCPKG_DOWNLOADSis already nonempty, preserve it for all workers and review commands. Use that shared directory only through vcpkg; never clean or delete it. Otherwise, do not set it.
index.md content
index.md must include:
- Coverage summary, including how many PRs were reviewed, skipped, or failed.
- PRs grouped by the shared guide's verdicts:
approve,approve-with-notes,request-changes, andunknown, with relative links to their reports. - Competing PRs grouped only by the specific modified ports they share.
- PRs with no touched
ports/<portname>/entries. - PRs that failed to review, with a short reason instead of silently omitting them.
Required output layout
Write only final deliverables under the fixed reviews-root, not under investigation-root:
index.mdatreviews-root.report.mdin each worker's{{REPORT_DIR}}, including the guide's self-contained## Fix handofffor use without this session's chat history.patches/*.patchin each worker's{{REPORT_DIR}}-- only forexamples-and-patches; omit if no patches were produced and explain any unpatched issues in the report.
Do not stop until the index and every reviewed PR's report exist at these absolute destinations and are complete.