Is commit-msg-gen safe to install?

SaferSkills independently audited commit-msg-gen (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.

commit-msg-gen/SKILL.md · 1 file

commit-msg-gen/SKILL.md1.7 KB · Markdown

name: commit-msg-gen

description: "Generate conventional commit messages without scope from staged changes. Use when: preparing commits with #git_diff_staged to create concise commit messages following conventional commits format."

argument-hint: "Optional: specify commit type (fix, feat, refactor, docs, etc.) or leave empty for auto-detection"

Conventional Commit Message Generator

Generate conventional commit messages following the Conventional Commits specification, without scope prefix.

When to Use

You have staged changes and need a properly formatted commit message
You want commit messages that follow conventional commits format
You need concise messages without scope (e.g., fix: description instead of fix(scope): description)

Procedure

Stage your changes using git add
Invoke this skill in chat
The skill will:

Fetch staged changes using #git_diff_staged
Analyze the changes to determine commit type (fix, feat, refactor, etc.)
Extract the primary file name from changes
Generate a conventional commit message in format: type: description in \FileName\``

Commit Message Format

type: description in `FileName`

Supported Types

fix - Bug fixes
feat - New features
refactor - Code refactoring
docs - Documentation changes
style - Code style changes (formatting, etc.)
test - Test additions or updates
chore - Build, dependencies, tooling

Examples

fix: improve form initialization and modal state handling based on fetch completion in `QualityCheckResultsModal`
feat: add authentication guard to protected routes in `AuthGuard`
refactor: simplify data validation logic in `FormValidator`

commit-msg-gen— agent skill

Is commit-msg-gen safe to install?

Conventional Commit Message Generator

When to Use

Procedure

Commit Message Format

Supported Types

Examples

Audit the pieces. Scan the whole. Decide.