SaferSkills independently audited 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.
✓—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
Every scanned point with the score it earned and what moved between them.
1 scans · 90 days
c73d40f
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
skills/commit/SKILL.md · 1 file
skills/commit/SKILL.md1.1 KB · Markdown
name: "commit"
description: "Stage + commit changes in semantic + reviewablegroups. Use when user wants to commit changes, organize commits, or clean up a branch before pushing."
git status --short first; scope to files from current task or explicit user request.
Leave unrelated dirty files alone unless user explicitly asks for a whole-tree commit.
Mixed tree: inspect diffs before staging; keep staged set one semantic change.
Stage by purpose, not git add ., unless whole task one coherent change.
Default one scoped conventional commit when task cohesive. Split only for clearly separate semantic groups. Optimize for reviewability.
Multiple commits: prefer order feat, fix, test, docs, refactor, chore.
Short scoped conventional messages; match what changed.
Each commit minimal, reviewable, one change type.
Between groups: git status -sb; confirm next commit has only intended files.
Ask before staging unrelated user changes, unfamiliar generated churn, or ambiguous dirty tree that makes ownership ambiguous.