git:20260408.a08708c to git:20260530.d3be4dd

12 added, 5 removed. Audit A to A.

---

name: release-audit

- description: Audit releases, tags, and assets for a repo or all repos in a directory. Finds orphaned tags, missing assets, and sr config issues. Use when checking release health.

- allowed-tools: Bash Read Grep Glob

+ description: >

+ 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.

+ allowed-tools: Bash(gh *), Bash(git *), Read, Grep, Glob

user-invocable: true

arguments:

- name: scope

description: "Path to a single repo or a directory of repos. Defaults to current directory."

required: false

---

# Release Audit

Audit releases, tags, and assets for consistency.

## Steps

1. **Determine scope**: If a directory of repos is given, discover all git repos one level deep. Otherwise use the current repo.

2. **For each repo**, gather:

- All tags: `git tag -l`

- All releases: `gh release list --limit 50 --json tagName,name,isDraft,isPrerelease,assets`

- - sr.yaml config (if present): read `sr.yaml` to understand expected release behavior

+ - **Detect sr.yaml**: check whether `sr.yaml` exists 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`, `v2` that point to the same commit as a full semver tag

3. **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**: missing config, misconfigured plugins, version file mismatches

+ - **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

4. **Report**: For each repo, show:

- ```

+ ```text

## 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

```

5. **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 `gh` isn't authenticated, fall back to git-only checks (tags, sr.yaml).

- For multi-repo scans, run checks in parallel where possible.