review-vcpkg-prs-today

작성자: microsoft

최근 30일 이내에 업데이트된 마이크로소프트/vcpkg의 오픈된 초안이 아닌 풀 리퀘스트를 검토합니다. 일괄 트라이지, PR별 검토 보고서, 그룹화된 인덱스 등이 요청될 때 사용합니다.

npx skills add https://github.com/microsoft/vcpkg --skill review-vcpkg-prs-today
ZIP 다운로드GitHub
27.5k

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로 웹앱을 계측하기 위한 지침입니다. 원격 분석 패턴, SDK 설정, 구성 참조를 제공합니다. WHEN: 앱 계측 방법, App Insights SDK, 원격 분석 패턴, App Insights란 무엇인가, Application Insights 지침, 계측 예시, APM 모범 사례.
devops
applicationinsights-web-ts
microsoft
브라우저/웹 앱을 Application Insights JavaScript SDK(@microsoft/applicationinsights-web)로 계측합니다. Real User Monitoring(RUM) — 페이지 뷰, 클릭, AJAX/fetch 종속성, 예외, 사용자 지정 이벤트, 백엔드 OpenTelemetry 트레이스와 상관관계가 있는 브라우저 측 GenAI 에이전트 트레이스에 사용합니다. SDK Loader Script 및 npm 설정, 프레임워크 확장(React, React Native, Angular), Click Analytics, 텔레메트리 이니셜라이저, 브라우저에서 생성된 에이전트/도구/모델 스팬에 대한 OTel GenAI 의미론적 규칙을 다룹니다.
devops
azure-ai-anomalydetector-java
microsoft
Azure AI Anomaly Detector SDK for Java로 이상 탐지 애플리케이션을 구축하세요. 단변량/다변량 이상 탐지, 시계열 분석 또는 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. ML 작업 영역, 작업, 모델, 데이터 세트, 컴퓨팅 및 파이프라인에 사용합니다. 트리거: "azure-ai-ml", "MLClient", "workspace", "model registry", "training jobs", "datasets".
development