review-vcpkg-prs-today

作者: microsoft

审查过去30天内更新的非草稿状态的microsoft/vcpkg拉取请求。用于批量分类、逐PR审查报告、按…分组的索引时使用。

npx skills add https://github.com/microsoft/vcpkg --skill review-vcpkg-prs-today

Inputs

InputRequiredMeaning
investigation-rootNoDirectory 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-depthNoOne 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

  1. Before changing directories, resolve investigation-root, reviews/, and .github/skills/shared/review-vcpkg-pr-guide.md against the caller's original directory to absolute paths. Keep the resolved reviews directory as reviews-root; never rebase it onto a worker's workspace.
  2. Discover candidates using GitHub search (gh api or the Search API), not the generic pulls list: repo:microsoft/vcpkg is:pr is:open draft:false updated:>=<today minus 30 days>. Prefer authentication via gh or GITHUB_TOKEN to avoid low unauthenticated limits.
  3. Fetch each candidate's changed files; identify ports from ports/<portname>/.
  4. Prepare isolated workspaces as below. Review every candidate independently with a general-purpose worker 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}} under reviews-root).
    • Absolute guide path.
  5. Write each report when completed. Write index.md last from the final per-PR results and port-specific competition groups.

Parallel execution safety

  1. 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.
  2. Create all isolated workspaces before launching workers. Copy the caller's vcpkg.exe (Windows) or vcpkg (non-Windows) into each workspace root.
  3. Use the caller's working tree only when exactly one worker is active and the user explicitly allows it.
  4. If VCPKG_DOWNLOADS is 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:

  1. Coverage summary, including how many PRs were reviewed, skipped, or failed.
  2. PRs grouped by the shared guide's verdicts: approve, approve-with-notes, request-changes, and unknown, with relative links to their reports.
  3. Competing PRs grouped only by the specific modified ports they share.
  4. PRs with no touched ports/<portname>/ entries.
  5. 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:

  1. index.md at reviews-root.
  2. report.md in each worker's {{REPORT_DIR}}, including the guide's self-contained ## Fix handoff for use without this session's chat history.
  3. patches/*.patch in each worker's {{REPORT_DIR}} -- only for examples-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.

来自 microsoft 的更多技能

oss-growth
microsoft
OSS增长黑客角色
agent-framework-azure-ai-py
microsoft
使用Microsoft Agent Framework Python SDK(agent-framework-azure-ai)构建Azure AI Foundry代理。在创建使用AzureAIAgentsProvider的持久化代理、使用托管工具(代码解释器、文件搜索、网络搜索)、集成MCP服务器、管理对话线程或实现流式响应时使用。涵盖函数工具、结构化输出和多工具代理。
development
airunway-aks-setup
microsoft
在AKS上设置AI Runway——从裸集群到运行模型。涵盖集群验证、控制器安装、GPU评估、提供商设置和首次部署。适用场景:“设置AI Runway”、“接入AKS集群”、“安装AI Runway”、“airunway设置”、“将模型部署到AKS”、“在AKS上进行GPU推理”、“在AKS上配置KAITO”、“在AKS上运行LLM”、“在AKS上使用vLLM”、“在AKS上设置模型服务”、“AI Runway控制器”。
devops
appinsights-instrumentation
microsoft
使用Azure Application Insights对Web应用进行插桩的指南。提供遥测模式、SDK设置和配置参考。适用场景:如何对应用进行插桩、App Insights SDK、遥测模式、什么是App Insights、Application Insights指南、插桩示例、APM最佳实践。
devops
applicationinsights-web-ts
microsoft
使用Application Insights JavaScript SDK(@microsoft/applicationinsights-web)为浏览器/Web应用添加检测。用于真实用户监控(RUM)——页面视图、点击、AJAX/fetch依赖项、异常、自定义事件,以及与后端OpenTelemetry追踪关联的浏览器端GenAI代理追踪。涵盖SDK加载器脚本和npm设置、框架扩展(React、React Native、Angular)、点击分析、遥测初始化器,以及从浏览器发出的代理/工具/模型跨度所遵循的OTel GenAI语义约定。
devops
azure-ai-anomalydetector-java
microsoft
使用适用于 Java 的 Azure AI 异常检测器 SDK 构建异常检测应用程序。在实现单变量/多变量异常检测、时间序列分析或 AI 驱动的监控时使用。
development
azure-ai-language-conversations-py
microsoft
使用azure-ai-language-conversations Python SDK实现对话语言理解(CLU)。当使用ConversationAnalysisClient分析对话意图和实体、构建NLP功能或将语言理解集成到应用程序中时使用。
development
azure-ai-ml-py
microsoft
Azure Machine Learning SDK v2 for Python。用于机器学习工作区、作业、模型、数据集、计算资源和管道。 触发词:“azure-ai-ml”、“MLClient”、“工作区”、“模型注册表”、“训练作业”、“数据集”。
development