create-changelog-affcfa — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited create-changelog-affcfa (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 changelog backfilled with version history.
/changelog-rules SkillRun /changelog-rules to load shared changelog conventions.
Collect release history from the most authoritative source available:
gh release list --limit 100 --json tagName,name,publishedAt,body to get release notes. For each release, parse the body into changelog entries.git tag --sort=-v:refname to list tags. For each consecutive tag pair, run git log <older-tag>..<newer-tag> --oneline to collect commit summaries.For each version, classify entries into the standard change types and apply the changelog-worthiness criteria per /changelog-rules.
If the changelog file already exists, warn the user and confirm before overwriting.
Write the changelog following the /changelog-rules file structure and conventions.
Briefly summarize how many versions were backfilled and which source was used (GitHub releases or git tags).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.