Is changelog safe to install?

SaferSkills independently audited 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.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/changelog/SKILL.md · 1 file

skills/changelog/SKILL.md2.2 KB · Markdown

name: changelog

description: Generate a CHANGELOG.md entry from git log since last tag — invoked via /changelog

allowed-tools: Bash, Read, Write, AskUserQuestion

disable-model-invocation: false

Changelog — generate changelog entry from git history

Activation

Invoked via /changelog. Use before any release or when CHANGELOG.md needs updating.

Process

Find the last git tag:

Bash: git describe --tags --abbrev=0 2>/dev/null || echo "none"

Get commits since that tag (or all commits if no tag):

Bash: git log --oneline --no-merges [last-tag]..HEAD 2>/dev/null If no tag: git log --oneline --no-merges | head -30

Read the existing CHANGELOG.md to understand the format.

Categorize the commits into:

Added / Changed / Fixed / Removed / Security Use the commit message as the source of truth. Ignore: chore, docs, style, test commits unless they are significant. Keep each item to one line, past tense, user-facing language.

Determine the version number:

If the user specified one, use it.
Otherwise, read the latest version from CHANGELOG.md and suggest

the next patch version (e.g. 1.0.0 → 1.0.1).

Use AskUserQuestion to confirm the version:

AskUserQuestion({ questions: [{ question: "Which version is this release?", header: "Version", multiSelect: false, options: [ { label: "[suggested patch]", description: "Increment patch version" }, { label: "[suggested minor]", description: "Increment minor version" }, { label: "[suggested major]", description: "Increment major version" }, { label: "I'll type it", description: "Provide a custom version string" } ] }] })

Write the new entry to CHANGELOG.md, inserting it after the

[Unreleased] section (or at the top if none exists).

Format:

[X.Y.Z] - YYYY-MM-DD

Added

Fixed

Confirm: "CHANGELOG.md updated. Review it before tagging."

Constraints

Never invent changes not in git log.
Never include internal refactoring or test changes unless significant.
Never overwrite existing entries — only insert above them.
Max 15 items total per entry. Summarize if more.

changelog— agent skill

Is changelog safe to install?

Changelog — generate changelog entry from git history

Activation

Process

[Unreleased] section (or at the top if none exists).

[X.Y.Z] - YYYY-MM-DD

Added

Fixed

Constraints

Audit the pieces. Scan the whole. Decide.