Is git-commit safe to install?

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

git-commit/SKILL.md · 1 file

git-commit/SKILL.md1.7 KB · Markdown

name: git-commit

description: 'Execute git commit with conventional commit. Use when user asks to create a git commit'

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.

Workflow

Analyze Diff

Stage Files (if needed)

Generate Commit Message

Execute Commit

Report commit result with URL to user

After successful commit, get the commit hash: git rev-parse HEAD
Get the remote URL: git remote get-url origin
Construct the commit URL:
If remote is GitHub (github.com): https://github.com/<owner>/<repo>/commit/<hash>
If remote is a GitHub mirror (e.g., git.sr.ht mirrors): extract the actual GitHub URL
Always include the full commit URL in your response to the user

Conventional Commit Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
Assisted-by: {HARNESS_NAME}:${MODEL_NAME}

Type: feat, fix, docs, style, refactor, test, chore, etc.
Scope: optional context (e.g., auth, api, ui)
Description: concise summary in imperative mood, aim for short message
Body: detailed explanation (optional)
Footer: metadata like Closes, BREAKING CHANGE. Always include Assisted-by: {HARNESS_NAME}:${MODEL_NAME}

Best Practices

Use atomic commits: one logical change per commit, split unrelated changes
Present tense: "add" not "added"
Imperative mood: "fix bug" not "fixes bug"
Reference issues: Closes #123, Refs #456
Write short, imperative commit messages

git-commit— agent skill

Is git-commit safe to install?

Git Commit with Conventional Commits

Overview

Workflow

Conventional Commit Format

Best Practices

Audit the pieces. Scan the whole. Decide.