release-audit
SolidAudit an existing GitHub release without changing it. Use when verifying exact-head CI, local and remote tag identity, public release state, or declared release assets such as checksums, SBOMs, signatures, and attestations; do not use it to publish or repair a release.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- fmind
- Repository
- fmind/dotfiles
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- Go
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
release-audit-agent
Read-only pre-commit and pre-GitHub release audit for secrets, privacy leaks, unrelated changes, generated artifacts, dependencies, licenses, and release hygiene.
release-audit
Release & supply-chain readiness audit: gathers evidence from real workflows, manifests, and repo settings, compares against a gold-standard reference stack, has an adversarial subagent try to refute the draft, and returns a prioritized action plan (P1–P3) whose fixes are delegated to the sibling setup skills. Use when asked to audit release automation, publishing security, CI or supply-chain maturity, or whether a repo is ready to release. For a whole-repo health check (docs, tests, code quality) use maturity-analysis instead.
magpie-release-audit-report
Assemble a per-release audit record from lifecycle artefacts (planning issue, vote thread, artefact list, promote revision, and announcement URL) and propose a PR appending it to the project's audit log. Read-only on every release surface; the only write is a PR the RM reviews and a committer merges.