skills.rest
vzco
vzcoOFFICIAL
Explore all skills by this author →
GitHub

gh-release-check

Compare published GitHub releases with local build artifacts using gh CLI.

15|4|Updated Mar 7, 2026
Search Tags:#github#workflow-automation#gh-cli#release-check#local-builds#version-validation#asset-verification
One-click install
npx skills add https://github.com/vzco/arc-probe --skill gh-release-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-release-check
Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/gh-release-check
Command: npx skills add https://github.com/vzco/arc-probe --skill gh-release-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping GitHub release assets in sync with local builds is error-prone and can lead to deployments of outdated binaries.

Core Features & Use Cases

  • List published releases from a GitHub repository to assess versioning and asset availability.
  • View release details and verify that required assets (e.g., probe.exe, probe-shell.dll) are present and up-to-date.
  • Compare published releases with local build artifacts to ensure alignment before distribution.

Quick Start

Run the GitHub Release Check against the public repository and compare assets with local builds.

Frequently Asked Questions about gh-release-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify GitHub releases against local builds to prevent outdated deployments?▼

To verify GitHub releases against local builds, you can list published releases, inspect assets using the gh CLI, and compare versions with local artifacts to identify discrepancies and ensure alignment before distribution.

What is GitHub release asset verification and when do I need it?▼

GitHub release asset verification is the process of comparing published release assets against local build artifacts. You need it for release validation workflows, asset integrity checks, and plugin-version alignment across repositories to prevent outdated binary deployments.

How do I check if required assets are present and up-to-date in a GitHub release?▼

You can check required assets by viewing release details and verifying that specific files like probe.exe or probe-shell.dll are present and up-to-date, comparing them directly against your local build artifacts for alignment.

Can I use gh CLI to automate release validation across multiple repositories?▼

Yes, you can use the gh CLI to automate release validation across repositories by listing published releases, inspecting assets, and comparing published versions with local build artifacts to ensure plugin-version alignment.

What's the best way to compare published GitHub releases with local build artifacts?▼

The best way to compare published releases with local build artifacts is to list releases via the gh CLI, inspect repository metadata and assets, then validate version alignment to catch discrepancies before distribution.

Why does my GitHub release contain outdated binaries compared to my local build?▼

Your GitHub release may contain outdated binaries because keeping release assets in sync with local builds is error-prone. Listing releases and inspecting assets against local artifacts helps identify these version discrepancies.

Related Skills

Explore More Software Engineering Skills→
hckhanhhckhanh
3

ctx-upgrade

Fetch, build, install, and configure the Context Mode plugin automatically.

Community
Intermediate
solo-istsolo-ist
2

release

Automate Prose release packaging, signing, and publishing for MAS and GitHub Releases.

Official
Advanced
HKUDSHKUDS
46.8k

github

Manage GitHub issues, pull requests, and workflow runs via the gh CLI.

Official
Intermediate
saif27217saif27217

github

Manage GitHub pull requests and workflow runs via the gh CLI.

Community
Intermediate