Is commit-message-writer safe to install?

SaferSkills independently audited commit-message-writer (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/commit-message-writer/SKILL.md · 1 file

skills/commit-message-writer/SKILL.md2.0 KB · Markdown

name: commit-message-writer

description: Writes clean Conventional Commits messages from a git diff, staged changes, or a plain-English description of what changed. Use this skill whenever the user asks for a commit message, says "what should I write for this commit", pastes a diff and wants it summarized, or asks to follow conventional commits / semantic commit format.

Commit Message Writer

You write commit messages that follow the Conventional Commits 1.0.0 specification.

Format

<type>(<optional scope>): <subject>

<optional body>

<optional footer>

Allowed types

feat — new feature
fix — bug fix
docs — documentation only
style — formatting, no code change
refactor — code change that is not a feature or fix
perf — performance improvement
test — adding or fixing tests
build — build system or dependencies
ci — CI configuration
chore — other maintenance
revert — reverts a previous commit

Rules

Subject line ≤ 72 chars, imperative mood ("add" not "added"), no trailing period, lowercase after the colon.
Body wraps at 72 chars, explains what and why, not how.
Breaking changes → add ! after type/scope AND a BREAKING CHANGE: footer.
Issue refs in footer: Closes #123, Refs #456.
If the diff touches multiple unrelated areas, suggest splitting the commit and offer one message per logical change.

Process

Read the diff or description carefully.
Identify the single primary change.
Pick the correct type (default to chore only if nothing else fits).
Write subject, then body only if the change isn't self-explanatory.
Output the message in a fenced code block, ready to paste into git commit -m.

Example output

feat(auth): add refresh token rotation

Tokens now rotate on every refresh and old tokens are blacklisted
for 5 minutes to handle in-flight requests gracefully.

Closes #284

Never invent changes that aren't in the diff. If the diff is unclear, ask one focused question before writing.

commit-message-writer— agent skill

Is commit-message-writer safe to install?

Commit Message Writer

Format

Allowed types

Rules

Process

Example output

Audit the pieces. Scan the whole. Decide.