release-check — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited release-check (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
make can-releasedon't include entries (the maintainer adds them at merge), so this is the last line of defense before a release is cut. List everything merged since the last tag and compare against the [Unreleased] section:
git describe --tags --abbrev=0
git log --oneline --no-merges vX.Y.Z..HEAD
awk '/^## \[Unreleased\]/{flag=1; next} /^## \[/{flag=0} flag' CHANGELOG.mdEvery user-facing change (feat, fix, breaking change — including merged community PRs) must have a bullet under ## [Unreleased]. Internal-only commits (ci, chore, docs about the repo itself, release/publish plumbing) don't need entries. PRs are squash-merged, so each main commit maps 1:1 to a PR via its (#N) suffix. For each user-facing commit with no matching bullet, report it as a failure and draft a suggested entry (source it from the PR description via gh pr view N, taking N from the commit subject's suffix).
If everything passes:
✅ Release check passed. All tests, linting (ruff + pyright), and formatting checks are green, and every user-facing change since the last tag has a CHANGELOG entry.
If something fails:
❌ Release check failed.
List each failing check with:
make test/verbose make formatmake can-release checksmake lint — ruff check + pyright type checkingmake test — full pytest suite~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.