write-changelog — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited write-changelog (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.
Keep CHANGELOG.md honest and current. Teams universally let changelogs rot — this skill drafts the entry from commit history so the human only needs to review and confirm, not write from scratch.
# What version are we releasing?
cat VERSION # or package.json version, pyproject.toml, etc.
# Commits since the last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline
# If no tags exist
git log --oneline -30Ask the user for the new version number if it is not clear from a VERSION file.
Map each commit to a Keep-a-Changelog section:
| Commit type | Section |
|---|---|
feat: | Added |
fix: | Fixed |
refactor:, perf: | Changed |
docs: | Changed (if user-visible) or skip |
| Removal of a feature | Removed |
BREAKING CHANGE: in body | Changed with a ⚠️ Breaking prefix |
chore:, style:, test:, ci: | Skip — internal, not user-facing |
Omit commits that are invisible to users (tooling, CI, test-only changes).
## [VERSION] — YYYY-MM-DD
### Added
- Short description of new capability. (#PR or commit ref)
### Changed
- Short description of changed behaviour. (#PR or commit ref)
### Fixed
- Short description of bug fixed. (#PR or commit ref)
### Removed
- Short description of removed feature. (#PR or commit ref)Rules:
YYYY-MM-DD).head -40 CHANGELOG.mdConfirm the existing format and insert the new entry at the top, below the # Changelog heading and above the previous release.
Show the drafted entry in a code block. Say: "Ready to prepend this to CHANGELOG.md?" Do not write the file until the user confirms.
Prepend the entry to CHANGELOG.md. Do not touch any other section.
A single Keep-a-Changelog section, ready to prepend to CHANGELOG.md.
CHANGELOG.md does not exist, create it with the standard header first: # Changelog
All notable changes to this project will be documented in this file.
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).[Unreleased] sections — write the version and date directly.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.