skill-urmzd-dotfiles-release-audit · by Install
$ agentstack add skill-urmzd-dotfiles-release-audit ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-urmzd-dotfiles-release-audit) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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:
```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
```
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: urmzd
- Source: urmzd/dotfiles
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.