Release audit
Audit GitHub releases, git tags, and release assets for one repo or every repo in a directory. Flags orphaned tags, missing binaries/checksums, draft releases, floating tag drift, pre-release remnants, and (when sr.yaml is present) sr config issues. Read-only: never deletes or modifies tags/releases. Use when checking "release health", "orphaned tags", "missing assets", "draft releases stuck", or "is sr.yaml configured right". Do NOT use to cut or publish a release, and do NOT use to set up the release pipeline -- this only audits and reports.From its SKILL.md
npx -y skills add urmzd/dotfiles --skill release-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 2 commands, including `git tag -l` and 1 more.
SKILL.md
2.7 KB, 513 tokens by cl100k_base, as published. Nobody here has run it
Release Audit
Audit releases, tags, and assets for consistency.
Steps
-
Determine scope: If a directory of repos is given, discover all git repos one level deep. Otherwise use the current repo.
-
For each repo, gather:
- All tags:
git tag -l - All releases:
gh release list --limit 50 --json tagName,name,isDraft,isPrerelease,assets - Detect sr.yaml: check whether
sr.yamlexists at the repo root. Only if present, read it to understand expected release behavior. If absent, skip all sr-specific checks for this repo (do not report a "missing sr.yaml" issue -- not every repo uses sr). - Floating tags: tags like
v1,v2that point to the same commit as a full semver tag
- All tags:
-
Check for issues:
- Orphaned tags: tags with no corresponding GitHub release
- Releases without assets: releases that should have binaries/checksums but don't
- Draft releases: releases stuck in draft state
- Floating tag drift: major version tags (e.g.,
v1) not pointing to the latest patch - sr.yaml issues (only when sr.yaml was detected in step 2): misconfigured plugins, version file mismatches between sr.yaml and the actual version files
- Pre-release remnants: old pre-release versions that were never promoted
-
Report: For each repo, show:
## repo-name - Latest release: v1.2.3 (2024-01-15) - Total releases: 12 | Tags: 15 - Issues: - ⚠ 3 orphaned tags: v0.1.0, v0.2.0, v0.3.0 - ⚠ Floating tag v1 behind latest (points to v1.1.0, latest is v1.2.3) - ✓ All releases have assets -
Summary: One-line-per-repo table at the end with issue counts.
Rules
- Don't delete or modify tags/releases. This is read-only audit.
- If
ghisn't authenticated, fall back to git-only checks (tags, sr.yaml). - For multi-repo scans, run checks in parallel where possible.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.