Skill

gh-release-check

Checks GitHub release status: lists versions, views details, verifies assets, compares with local builds, aligns plugin versions. Useful for release verification workflows.

Github

Git

npx claudepluginhub vzco/arc-probe --plugin arc-probe

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Verify the state of published releases and compare with local builds.

SKILL.md

Similar Skills

release

Builds Tauri binaries for ARC Probe, packages CLI zip and NSIS installer, creates GitHub release assets including updater manifest and README, updates versions, and publishes to GitHub.

arc-probe

github-release

689

Sanitizes GitHub repos for public release (secrets scan, artifact removal, LICENSE/README validation) then creates tags and publishes via gh CLI.

2 files

dev-tools

check-version

Checks bopen-tools plugin version against GitHub in ~70ms, returning JSON status (current/outdated/ahead). Use at session start, for update queries, or suspicious skill behavior.

1 file1 tool

bopen-tools

Stats

Parent Repo Stars10

Parent Repo Forks3

Last CommitMar 8, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

ARC Probe — GitHub Release Check

Verify the state of published releases and compare with local builds.

Steps

1. List published releases

cd public-repo gh release list

2. Check latest release details

gh release view <tag>

Look for:

Release title and tag

Assets (zip file should be present)

Download count

Published date

3. Verify asset contents

# Download and inspect gh release download <tag> -D /tmp/arc-probe-check cd /tmp/arc-probe-check powershell -NoProfile -Command "Expand-Archive -Path '*.zip' -DestinationPath './extracted'" ls -lh extracted/

Should contain: probe.exe, probe-inject.exe, probe-shell.dll, README.md

4. Compare with local build

# Check if local binaries are newer ls -lh build/probe.exe build/probe-inject.exe build/probe-shell.dll

If local files are newer than the release, consider a new release.

5. Check plugin version alignment

# Plugin version in repo grep '"version"' plugin/.claude-plugin/plugin.json # Marketplace version grep -A2 '"arc-probe"' public-repo/.claude-plugin/marketplace.json | grep version # Latest release tag gh release list --limit 1

All three should match. If they don't, run /arc-probe:bump-version and /arc-probe:release.

ARC Probe — GitHub Release Check

Verify the state of published releases and compare with local builds.

Steps

1. List published releases

cd public-repo
gh release list

2. Check latest release details

gh release view <tag>

Look for:

Release title and tag
Assets (zip file should be present)
Download count
Published date

3. Verify asset contents

# Download and inspect
gh release download <tag> -D /tmp/arc-probe-check
cd /tmp/arc-probe-check
powershell -NoProfile -Command "Expand-Archive -Path '*.zip' -DestinationPath './extracted'"
ls -lh extracted/

Should contain: probe.exe, probe-inject.exe, probe-shell.dll, README.md

4. Compare with local build

# Check if local binaries are newer
ls -lh build/probe.exe build/probe-inject.exe build/probe-shell.dll

If local files are newer than the release, consider a new release.

5. Check plugin version alignment

# Plugin version in repo
grep '"version"' plugin/.claude-plugin/plugin.json

# Marketplace version
grep -A2 '"arc-probe"' public-repo/.claude-plugin/marketplace.json | grep version

# Latest release tag
gh release list --limit 1

All three should match. If they don't, run /arc-probe:bump-version and /arc-probe:release.