release — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited release (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.
Create a release for mor. The user provides the version number (e.g. /release v0.12.0).
v if present to get the semver (e.g. 0.12.0). The tag uses v prefix (e.g. v0.12.0).pnpm prepublishOnly (lint, test, build) before making any changes. If it fails, stop and fix the issues first.gh release list --limit 1 to get the latest release tag.git log <previous-tag>..HEAD --oneline to get all commits since the last release. Group them into sections:Skip version bump commits. Write concise user-facing descriptions, not raw commit messages.
version in package.json, .claude-plugin/plugin.json, and the .TH header line of man/mor.1 to the new semver. The .TH line in man/mor.1 also carries a release date — update it to today's date in YYYY-MM-DD format. Format: .TH MOR 1 "<date>" "mor <semver>" "User Commands".<semver> (e.g. 0.12.0), then push.gh release create v<semver> with the changelog as the body. Use ## What's new as the top-level heading.publish.yml GitHub Actions workflow, triggered by the v* tag created in step 8. No manual publish step is needed.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.