Score breakdown0 Version history1 Source
Category Weight Category score Contribution
Security prompt, exec, net, exfil, eval
35%
100
35.0 pts
Supply chain hash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenance staleness, pinning, CI
15%
100
15.0 pts
Transparency SKILL.md, perms, README
15%
100
15.0 pts
Community installs, verify, response
15%
100
15.0 pts
Findings & checks · 0 flagged
Security score 100 · 0 findings
✓ — All security checks passedNo findings in this category for the latest scan. pass
Supply chain score 100 · 0 findings
✓ — All supply chain checks passedNo findings in this category for the latest scan. pass
Maintenance score 100 · 0 findings
✓ — All maintenance checks passedNo findings in this category for the latest scan. pass
Transparency score 100 · 0 findings
✓ — All transparency checks passedNo findings in this category for the latest scan. pass
Community score 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 7c5d0b7 latest
Jun 23, 2026 100 7c5d0b7
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.md 1.7 KB · Markdown Rendered Raw ⧉ Copy
description : Commit changes with well-crafted messages, grouping related files into separate commits
argument-hint : "[optional commit message or instructions]"
Workflow Run these commands in parallel to understand the current state: git status — see all tracked/untracked files and staging stategit diff — see unstaged changesAnalyze ALL changes (staged + unstaged) and determine what should be committed: If there are no changes at all, inform the user and stop Do NOT commit files that likely contain secrets (.env, credentials, tokens, API keys). Warn the user if such files are present. Group related file changes into logical commits: Do NOT lump all changes into a single commit Examine each changed file and understand what it does Group files that are part of the same logical change together (e.g., a component + its styles + its test = one commit) Each group becomes its own commit If only one logical change exists, one commit is fine For each group, draft a commit message: Write natural, concise descriptions of what changed and why Do NOT use conventional commits format (no feat:, fix:, chore: prefixes) Keep the subject line under 72 characters If the user provided a message or instructions via arguments, incorporate or use that for the relevant commit(s) For each group, stage and commit: git add <specific files> for that group onlygit commit -m "message"Repeat for each group in a logical order (foundational changes first) Run git status after all commits to verify everything is clean. Report the result: show each commit hash and summary. User Arguments $ARGUMENTS