[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B6ABGAKDJYC1MPKGZ9CCJ":3,"skill-same:01M69B6ABGAKDJYC1MPKGZ9CCJ":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M69B6ABGAKDJYC1MPKGZ9CCJ","evaluate-new-port",null,"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.","microsoft\u002Fvcpkg","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B5ZTTQSKDYEXJ8P93R330",27597,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fevaluate-new-port\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"new","evaluate new port","evaluate","port","build","port review","sources","recipe","name","dependencies","review","files","audit","metadata","license","report","code","vcpkg","2026-11-10 10:12:30",false,"---\nname: evaluate-new-port\ndescription: '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.'\nargument-hint: 'Port name (e.g. \"libpng\")'\n---\n\n# Evaluate New Port\n\n## When to Use\n\n- Reviewing a newly added or substantially updated port\n- Auditing whether a port's declared license metadata matches what it installs\n- Checking for vendored third-party code or optional dependencies that are not modeled in `vcpkg.json`\n- Looking for packaging or review issues after a real local install\n\n## Overview\n\nThis skill takes a single port name, reads the port's metadata and build recipe, performs a clean local install, and writes a structured audit report. The audit focuses on:\n\n- **Declared license metadata** from `ports\u002F{port-name}\u002Fvcpkg.json`, including feature-scoped declarations\n- **Build invocation** and feature toggles from `ports\u002F{port-name}\u002Fportfile.cmake`\n- **Real build output** after `vcpkg x-ci-clean` and `vcpkg install {port-name}`\n- **Extracted source tree** under `buildtrees\u002F{port-name}\u002Fsrc`\n- **Installed package contents** under `packages\u002F{port-name}_{target-triplet}`\n- **Code review suggestions** for the port's packaging logic and metadata\n\nIf the install reports that the port is unsupported on the current platform or triplet, stop there and recommend a more appropriate platform instead of continuing the audit.\n\n## Required Inputs\n\n- A valid port name present under `ports\u002F{port-name}`\n\n## Detailed Workflow\n\n### Step 1: Read the Port Metadata\n\nOpen these files first:\n\n- `ports\u002F{port-name}\u002Fvcpkg.json`\n- `ports\u002F{port-name}\u002Fportfile.cmake`\n\nExtract at least the following:\n\n**From `vcpkg.json`:**\n- top-level `license`, if present\n- any feature-scoped `license` declarations, including explicit `null`\n- `homepage`\n- `features`\n- `dependencies`\n- `supports`, if present\n\n**From `portfile.cmake`:**\n- The primary build helper used (`vcpkg_cmake_configure`, `vcpkg_configure_make`, `vcpkg_cmake_build`, Meson helpers, raw `cmake`, etc.)\n- Feature-to-build-option mappings\n- Explicit enable\u002Fdisable flags for optional upstream components\n- Any platform guards, fatal errors, or unsupported conditions\n- Any bundling, patching, or file-pruning logic relevant to installed content\n\n### Step 2: Clean the Local Working State\n\nRun the repository-local vcpkg executable from the repository root:\n\n**Windows:**\n```powershell\n.\\vcpkg.exe x-ci-clean\n```\n\n**Linux\u002FmacOS:**\n```bash\n.\u002Fvcpkg x-ci-clean\n```\n\nDo not skip this step. The audit should be based on a fresh source extraction and package install.\n\n### Step 3: Install the Port\n\nRun a normal install of the requested port:\n\n**Windows:**\n```powershell\n.\\vcpkg.exe install {port-name}\n```\n\n**Linux\u002FmacOS:**\n```bash\n.\u002Fvcpkg install {port-name}\n```\n\nCapture the output. If it contains an unsupported-platform message, stop the workflow and report:\n\n1. That the current platform cannot evaluate this port meaningfully\n2. The reason quoted from the install output or `portfile.cmake`\n3. A suggested alternate platform, chosen from evidence in `supports`, platform guards, or fatal-error text\n\nCommon examples:\n- `only supports Windows` → suggest Windows\n- `only supports Linux` → suggest Linux\n- `only supports x64 and x86 Windows` → suggest an x64 Windows host\n- `Building for {TARGET_TRIPLET} on {HOST_TRIPLET} is unsupported` → suggest the native target platform instead of cross-building\n\nIf the install succeeds, continue.\n\nIf the install hit a binary cache and you need to rerun the port to force a local rebuild for inspection, remove and reinstall the affected port directly rather than running `x-ci-clean` followed by `install --no-binarycaching`. That preserves cache hits for unedited dependencies while still rebuilding the port under review.\n\n### Step 4: Determine the Installed Triplet Directory\n\nFind the installed package directory under:\n\n```text\npackages\u002F{port-name}_{target-triplet}\n```\n\nUse the package directory that was created by the install you just ran. The triplet is normally the system default target triplet (for example `x64-windows`, `arm64-windows`, or `x64-linux`).\n\nIf multiple matching directories exist, prefer the one whose timestamp matches the current install output. Record the chosen triplet in the report.\n\n### Step 5: Audit the Extracted Source Tree\n\nInspect `buildtrees\u002F{port-name}\u002Fsrc` and identify the extracted source directory or directories for the current build. Review them for vendoring and undeclared optional dependencies.\n\n#### 5a. Vendored Dependencies\n\nLook for signs of bundled third-party code, such as directories or files named:\n\n- `third_party`\n- `third-party`\n- `vendor`\n- `vendors`\n- `extern`\n- `external`\n- `deps`\n- `dependencies`\n- `subprojects`\n- nested copies of well-known libraries\n\nFor each candidate:\n- identify the bundled project if possible\n- determine whether it is built or installed\n- check whether the same dependency is already modeled in `vcpkg.json`\n- note whether the portfile patches it out, replaces it with a vcpkg dependency, or leaves it vendored\n\n#### 5b. Optional Dependencies Not Explicitly Controlled\n\nLook for optional integrations that are present upstream but not clearly controlled in packaging. Sources of evidence include:\n\n- `find_package(...)`\n- `pkg_check_modules(...)`\n- `option(...)`\n- `WITH_*`, `ENABLE_*`, `USE_*`, `BUILD_*`\n- Meson `feature` or `dependency(...)`\n- Autotools `--with-*` \u002F `--enable-*`\n\nFlag an issue when an optional dependency:\n\n- appears in upstream build logic,\n- is not declared in `vcpkg.json`, and\n- is not explicitly enabled or disabled by `portfile.cmake`\n\nThe point is to find dependencies that may be auto-detected from the host environment, leading to non-reproducible builds.\n\n### Step 6: Audit Installed Content Against the Declared License Metadata\n\nInspect the package contents under `packages\u002F{port-name}_{target-triplet}`. Focus on:\n\n- `share\u002F{port-name}\u002Fcopyright`\n- installed license files\n- headers, sources, examples, tools, or assets originating from bundled third-party code\n- any embedded notices for code under additional licenses\n\nTreat explicit `\"license\": null` as intentional metadata meaning \"no SPDX expression is provided here; inspect the installed copyright file.\" Do not report that case as missing metadata by itself.\n\nFlag content when:\n\n- the installed files include third-party components under licenses not covered by the declared license metadata,\n- multiple upstream licenses appear to require a more precise SPDX expression,\n- or the package installs bundled code whose license is absent from the declared metadata and copyright file\n\nDo not assume every extra notice is a bug. Record the evidence and explain whether it appears compatible, incomplete, or suspicious.\n\n### Step 7: Review the Portfile for Packaging Suggestions\n\nWhile auditing `ports\u002F{port-name}\u002Fportfile.cmake`, look for common review items such as:\n\n- missing explicit disable flags for tests, docs, examples, benchmarks, or tools\n- optional dependencies that should be feature-gated\n- vendored libraries that could be replaced with vcpkg dependencies\n- install steps that might ship unnecessary files\n- missing cleanup of debug-only or duplicate artifacts\n- support restrictions that should move into `supports` in `vcpkg.json`\n- license metadata that is too broad or incomplete after considering top-level and feature-scoped declarations\n\nOnly report suggestions supported by evidence from the files or the install result.\n\n## Output Requirements\n\nGenerate a markdown report with these sections:\n\n1. **Port Summary**\n2. **Declared Metadata**\n3. **Build Invocation Summary**\n4. **Install Result**\n5. **Vendored Dependencies**\n6. **Optional Dependency Risks**\n7. **License \u002F Installed Content Findings**\n8. **Other Port Review Suggestions**\n9. **Recommended Follow-ups**\n\nBe specific. Cite file paths and brief snippets when they support a finding.\n\nIf there are no findings for a section, write `None found` instead of omitting the section.\n\n## Suggested Report Template\n\nSee `references\u002Freport-template.md`.\n\n## Execution Notes\n\n- Run from the repository root\n- Prefer repository-local paths in all findings\n- Do not continue source\u002Fpackage inspection after an unsupported install result\n- Base conclusions on the actual installed package directory created by this run\n- Keep the final report focused on actionable review feedback rather than restating raw command output\n","# Evaluate New Port\n\n## When to Use\n\n- Reviewing a newly added or substantially updated port\n- Auditing whether a port's declared license metadata matches what it installs\n- Checking for vendored third-party code or optional dependencies that are not modeled in `vcpkg.json`\n- Looking for packaging or review issues after a real local install\n\n## Overview\n\nThis skill takes a single port name, reads the port's metadata and build recipe, performs a clean local install, and writes a structured audit report. The audit focuses on:\n\n- **Declared license metadata** from `ports\u002F{port-name}\u002Fvcpkg.json`, including feature-scoped declarations\n- **Build invocation** and feature toggles from `ports\u002F{port-name}\u002Fportfile.cmake`\n- **Real build output** after `vcpkg x-ci-clean` and `vcpkg install {port-name}`\n- **Extracted source tree** under `buildtrees\u002F{port-name}\u002Fsrc`\n- **Installed package contents** under `packages\u002F{port-name}_{target-triplet}`\n- **Code review suggestions** for the port's packaging logic and metadata\n\nIf the install reports that the port is unsupported on the current platform or triplet, stop there and recommend a more appropriate platform instead of continuing the audit.\n\n## Required Inputs\n\n- A valid port name present under `ports\u002F{port-name}`\n\n## Detailed Workflow\n\n### Step 1: Read the Port Metadata\n\nOpen these files first:\n\n- `ports\u002F{port-name}\u002Fvcpkg.json`\n- `ports\u002F{port-name}\u002Fportfile.cmake`\n\nExtract at least the following:\n\n**From `vcpkg.json`:**\n- top-level `license`, if present\n- any feature-scoped `license` declarations, including explicit `null`\n- `homepage`\n- `features`\n- `dependencies`\n- `supports`, if present\n\n**From `portfile.cmake`:**\n- The primary build helper used (`vcpkg_cmake_configure`, `vcpkg_configure_make`, `vcpkg_cmake_build`, Meson helpers, raw `cmake`, etc.)\n- Feature-to-build-option mappings\n- Explicit enable\u002Fdisable flags for optional upstream components\n- Any platform guards, fatal errors, or unsupported conditions\n- Any bundling, patching, or file-pruning logic relevant to installed content\n\n### Step 2: Clean the Local Working State\n\nRun the repository-local vcpkg executable from the repository root:\n\n**Windows:**\n```powershell\n.\\vcpkg.exe x-ci-clean\n```\n\n**Linux\u002FmacOS:**\n```bash\n.\u002Fvcpkg x-ci-clean\n```\n\nDo not skip this step. The audit should be based on a fresh source extraction and package install.\n\n### Step 3: Install the Port\n\nRun a normal install of the requested port:\n\n**Windows:**\n```powershell\n.\\vcpkg.exe install {port-name}\n```\n\n**Linux\u002FmacOS:**\n```bash\n.\u002Fvcpkg install {port-name}\n```\n\nCapture the output. If it contains an unsupported-platform message, stop the workflow and report:\n\n1. That the current platform cannot evaluate this port meaningfully\n2. The reason quoted from the install output or `portfile.cmake`\n3. A suggested alternate platform, chosen from evidence in `supports`, platform guards, or fatal-error text\n\nCommon examples:\n- `only supports Windows` → suggest Windows\n- `only supports Linux` → suggest Linux\n- `only supports x64 and x86 Windows` → suggest an x64 Windows host\n- `Building for {TARGET_TRIPLET} on {HOST_TRIPLET} is unsupported` → suggest the native target platform instead of cross-building\n\nIf the install succeeds, continue.\n\nIf the install hit a binary cache and you need to rerun the port to force a local rebuild for inspection, remove and reinstall the affected port directly rather than running `x-ci-clean` followed by `install --no-binarycaching`. That preserves cache hits for unedited dependencies while still rebuilding the port under review.\n\n### Step 4: Determine the Installed Triplet Directory\n\nFind the installed package directory under:\n\n```text\npackages\u002F{port-name}_{target-triplet}\n```\n\nUse the package directory that was created by the install you just ran. The triplet is normally the system default target triplet (for example `x64-windows`, `arm64-windows`, or `x64-linux`).\n\nIf multiple matching directories exist, prefer the one whose timestamp matches the current install output. Record the chosen triplet in the report.\n\n### Step 5: Audit the Extracted Source Tree\n\nInspect `buildtrees\u002F{port-name}\u002Fsrc` and identify the extracted source directory or directories for the current build. Review them for vendoring and undeclared optional dependencies.\n\n#### 5a. Vendored Dependencies\n\nLook for signs of bundled third-party code, such as directories or files named:\n\n- `third_party`\n- `third-party`\n- `vendor`\n- `vendors`\n- `extern`\n- `external`\n- `deps`\n- `dependencies`\n- `subprojects`\n- nested copies of well-known libraries\n\nFor each candidate:\n- identify the bundled project if possible\n- determine whether it is built or installed\n- check whether the same dependency is already modeled in `vcpkg.json`\n- note whether the portfile patches it out, replaces it with a vcpkg dependency, or leaves it vendored\n\n#### 5b. Optional Dependencies Not Explicitly Controlled\n\nLook for optional integrations that are present upstream but not clearly controlled in packaging. Sources of evidence include:\n\n- `find_package(...)`\n- `pkg_check_modules(...)`\n- `option(...)`\n- `WITH_*`, `ENABLE_*`, `USE_*`, `BUILD_*`\n- Meson `feature` or `dependency(...)`\n- Autotools `--with-*` \u002F `--enable-*`\n\nFlag an issue when an optional dependency:\n\n- appears in upstream build logic,\n- is not declared in `vcpkg.json`, and\n- is not explicitly enabled or disabled by `portfile.cmake`\n\nThe point is to find dependencies that may be auto-detected from the host environment, leading to non-reproducible builds.\n\n### Step 6: Audit Installed Content Against the Declared License Metadata\n\nInspect the package contents under `packages\u002F{port-name}_{target-triplet}`. Focus on:\n\n- `share\u002F{port-name}\u002Fcopyright`\n- installed license files\n- headers, sources, examples, tools, or assets originating from bundled third-party code\n- any embedded notices for code under additional licenses\n\nTreat explicit `\"license\": null` as intentional metadata meaning \"no SPDX expression is provided here; inspect the installed copyright file.\" Do not report that case as missing metadata by itself.\n\nFlag content when:\n\n- the installed files include third-party components under licenses not covered by the declared license metadata,\n- multiple upstream licenses appear to require a more precise SPDX expression,\n- or the package installs bundled code whose license is absent from the declared metadata and copyright file\n\nDo not assume every extra notice is a bug. Record the evidence and explain whether it appears compatible, incomplete, or suspicious.\n\n### Step 7: Review the Portfile for Packaging Suggestions\n\nWhile auditing `ports\u002F{port-name}\u002Fportfile.cmake`, look for common review items such as:\n\n- missing explicit disable flags for tests, docs, examples, benchmarks, or tools\n- optional dependencies that should be feature-gated\n- vendored libraries that could be replaced with vcpkg dependencies\n- install steps that might ship unnecessary files\n- missing cleanup of debug-only or duplicate artifacts\n- support restrictions that should move into `supports` in `vcpkg.json`\n- license metadata that is too broad or incomplete after considering top-level and feature-scoped declarations\n\nOnly report suggestions supported by evidence from the files or the install result.\n\n## Output Requirements\n\nGenerate a markdown report with these sections:\n\n1. **Port Summary**\n2. **Declared Metadata**\n3. **Build Invocation Summary**\n4. **Install Result**\n5. **Vendored Dependencies**\n6. **Optional Dependency Risks**\n7. **License \u002F Installed Content Findings**\n8. **Other Port Review Suggestions**\n9. **Recommended Follow-ups**\n\nBe specific. Cite file paths and brief snippets when they support a finding.\n\nIf there are no findings for a section, write `None found` instead of omitting the section.\n\n## Suggested Report Template\n\nSee `references\u002Freport-template.md`.\n\n## Execution Notes\n\n- Run from the repository root\n- Prefer repository-local paths in all findings\n- Do not continue source\u002Fpackage inspection after an unsupported install result\n- Base conclusions on the actual installed package directory created by this run\n- Keep the final report focused on actionable review feedback rather than restating raw command output\n",{"name":5,"description":7,"argument-hint":42},"Port name (e.g. \"libpng\")","master","9a5dfef5d1a0438a7d24856a85bd60f309d355e9",".github\u002Fskills\u002Fevaluate-new-port",7803,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 01:14:19",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add microsoft\u002Fvcpkg --skill evaluate-new-port",{"tool":58,"command":59},"bunx","bunx skills add microsoft\u002Fvcpkg --skill evaluate-new-port",{"tool":61,"command":62},"pnpm","pnpm dlx skills add microsoft\u002Fvcpkg --skill evaluate-new-port","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fevaluate-new-port\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Freport-template.md","REFERENCE","参考文档",1157,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fevaluate-new-port\u002Freferences\u002Freport-template.md",[73,98,109,130,151,180],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":37},"01M69B6M5Z84YRH3JTD7MA4RNB","review-vcpkg-prs-today","Review open non-draft microsoft\u002Fvcpkg 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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Freview-vcpkg-prs-today\u002FSKILL.md",[],[29,36,80,81,82,9,83,84,85,86,87,88,89,90,91,92,93,22,94,95,96,97],"review vcpkg prs today","prs","triage","pull requests","pr review","pr","pull","batch","open","use","reports","grouping","draft","verdict","last","true","for","when",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":37},"01M69B6HS26Q5D5G4S4KSQ4MMA","review-vcpkg-pr","Review a microsoft\u002Fvcpkg pull request end-to-end.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Freview-vcpkg-pr\u002FSKILL.md",[],[29,85,36,105,9,106,86,107,95,108],"review vcpkg pr","pull request","end","request",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":37},"01M69B6FKYTWZYW9NDTBNMGHX5","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Ffix-reviewed-vcpkg-pr\u002FSKILL.md",[],[85,36,116,117,29,118,88,89,119,120,121,122,123,124,96,125,126,127,81,128,129],"fix reviewed vcpkg pr","fix","push","never","only","up","do","submit","reviews","fixes","Existing","review report","contributor","generic",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":37},"01M69B6D358PXX6B15701K4G2Y","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Ffetch-vcpkg-ci-logs\u002FSKILL.md",[],[36,137,138,139,140,141,142,143,144,145,32,146,147,89,148,149,96,97,150],"fetch vcpkg ci logs","logs","ci","fetch","ci logs","azure devops","azure","tasks","artifacts","reporting","analyze","devops","evidence","2026",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":167,"publishedAt":37},"01M69B67FGSCYXN7XK725CBF8Q","code-review","Review microsoft\u002Fvcpkg pull requests in GitHub Copilot code review. Check port correctness, packaging, dependencies, licenses, and consumer integration; validate examples when the review time budget permits.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fcode-review\u002FSKILL.md",[157,162],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":163,"categoryName":164,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[168,29,35,169,9,83,170,171,172,36,86,173,174,175,176,28,177,22,178,179,97],"code review","github","github copilot","validate","copilot","examples","integration","check","packaging","time","correctness","requests",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":37},"01M69B63DR7JASH6MKBM7MGVCZ","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.\nUSE FOR: explicit requests for CI regression triage, a failure inventory, baseline classification, action recommendations, or a formal CI failure report.\nDO 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.\n**ANALYSIS SKILL** USES: locally collected CI logs, vcpkg baselines, Azure DevOps metadata.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvcpkg\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fanalyze-ci-failures\u002FSKILL.md",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000023","Skill与智能体开发",[190,139,147,191,82,142,143,192,36,138,193,194,195,196,197,198,199,140,200,141,201,97],"analyze ci failures","analyze ci","debugging","actions","analysis","inventory","regression","ports","acquisition","question","local","general coding"]