commit-message — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited commit-message (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Produce a structured, Conventional Commits-compliant commit message from the staged diff — not a free-form summary. Separate from pre-commit-check (which audits the staged diff for issues; this writes the message after the audit passes).
git diff --cached # staged changes — the primary input
git log --oneline -10 # recent messages — infer repo's convention and scope patterns| Type | Use when |
|---|---|
feat | New capability visible to a user or caller |
fix | Corrects a defect or wrong behaviour |
refactor | Restructures code without changing observable behaviour |
docs | Changes to documentation only |
test | Adds or fixes tests |
chore | Build scripts, CI config, dependency bumps, tooling |
perf | Measurable performance improvement |
style | Formatting, whitespace — no logic change |
Pick the single most accurate type. If the diff spans multiple types, pick the dominant one and note the others in the body.
Derive scope from the primary directory or module affected:
| Changed path | Scope example |
|---|---|
src/auth/ | auth |
skills/core/commit-message/ | commit-message |
hooks/git-guard.sh | hooks |
| Root-level config only | omit scope |
Use the repo's recent log as a reference — match existing scope conventions if present.
type(scope): imperative description of what changedRules:
Add a body when:
Separate subject from body with a blank line. Wrap body at 72 characters.
For breaking changes, append:
BREAKING CHANGE: <what changed and how callers must adapt>Present the commit message in a code block, ready to copy:
type(scope): subject
Optional body explaining the why, not the what.Then ask: "Ready to commit with this message, or would you like to adjust it?"
Do not run git commit — that is the user's decision.
A single commit message block. No explanation unless the type choice is non-obvious.
git commit -m or make the commit. Write the message only.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.