Menu
Check for upstream project updates and newer versions. Use when asked to check for updates, compare versions, or see if a port is outdated.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Detect OS/shell, validate vcpkg setup, and emit a combined environment report. Use when asked to check the environment, verify setup, or troubleshoot vcpkg configuration.
Create a new vcpkg port with portfile.cmake, vcpkg.json, and patches. Use when asked to create, add, or generate a new port for a project.
Install a vcpkg port with overlay-ports and analyze build logs. Use when asked to install, test, or build a port.
Review port files against vcpkg guidelines and best practices. Use when asked to review, validate, or check a port for correctness.
Search for existing vcpkg ports by name, GitHub URL, or keywords in the local registry and upstream microsoft/vcpkg repository. Use when asked to find, search, or check if a port exists.
Update an existing port to a newer upstream version with SHA512 calculation and testing. Use when asked to update, upgrade, or bump a port version.
| name | check-port-upstream |
| description | Check for upstream project updates and newer versions. Use when asked to check for updates, compare versions, or see if a port is outdated. |
Monitor upstream project for new releases and compare with current port version in local registry and microsoft/vcpkg.
Supported Patterns:
openssl3, cpuinfo, tensorflow-liteopenssl3, zlib-ng, cpuinfo (batch check)check if openssl3 has updatesports/{port-name}/vcpkg.json — extract version, homepageports/{port-name}/portfile.cmake — extract REPO, REF, SHA512homepage or REPO value{github-url}/releases/latest or GitHub APIpath:ports/{port-name} filename:vcpkg.jsonvcpkg.json from raw.githubusercontent.comversions/{first-letter}-/{port-name}.jsonCHANGELOG.md, CHANGES.md, NEWS.md)Output a markdown report with these headings (in order). Emit all headings even if empty (use None).
# Port Upstream Check Report## Summary — Port, timestamp, outcome (UP-TO-DATE/PATCH AVAILABLE/MAJOR UPDATE/AHEAD OF UPSTREAM/NOT FOUND), versions## Sources — Homepage, GitHub repo, release source type## Versions — Local, upstream project, microsoft/vcpkg, REF pattern## Comparison — Local vs upstream, local vs microsoft/vcpkg, version age## Release Details — Latest tag, release date, tag prefix handling, changelog files## Breaking Change Indicators — Keywords found, potential risk level## Status — Classification summary, security fix mention## Recommendations — Upgrade commands, delay suggestions, contribution opportunities## Next Steps — Ordered list tailored to outcomeAdd ## Batch Summary table and ## Ports Requiring Action / ## Up-to-Date Ports sections.
CVE or security → flagupdate-port skill