commit-1249f3 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited commit-1249f3 (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.
Creates a well-formed Conventional Commits commit from the current working tree. Reads the diff, proposes a message for approval, then commits. Never commits silently — the user always sees and approves the message first.
| Flag | Effect |
|---|---|
--push | git push after a successful commit |
--british | British English spelling in the message (default: American English) |
--credit | Append Co-Authored-By: Claude trailer to the commit |
--all | Stage all modified/deleted tracked files before committing (equivalent to git add -u) |
--staged | Commit only what is already staged; never touch the index |
--breaking | Mark as a breaking change (appends ! and adds BREAKING CHANGE: footer) |
--amend | Amend the last commit instead of creating a new one |
--closes N | Append Closes #N footer |
--refs N | Append Refs #N footer |
If the user provides a free-text hint (e.g. /commit fix the login redirect loop), use it as a strong signal for the description — do not ignore it.
<type>[optional scope]: <description>
<body>
[optional footers]Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore Scope: noun in parentheses describing the section of the codebase (e.g. feat(auth):) Breaking change: append ! after type/scope AND add BREAKING CHANGE: <explanation> footer Description: imperative mood, no period at the end, lowercase after the colon Body: starts one blank line after the description; explains what and why, not how
--staged → use index as-is.--all → run git add -u (tracked files only; never git add .).git add -u and inform the user.
Run these in parallel:
git status --short — working tree overview.git diff --cached --stat + git diff --cached — staged changes (what will be committed).git diff --stat — unstaged changes (for awareness).git log --oneline -5 — recent commit style reference.git rev-parse --abbrev-ref HEAD.main or master: pause and require explicit confirmation beforeproceeding. State the branch name clearly. Do not commit until the user says yes.
--all or defaulting to git add -u).env*, *credentials*, *secret*, *token*,*.pem, *.key, *.p12, lock files over 1 MB.
src/auth/ → scope authsrc/api/ and tests/api/ → scope apiCompose a full draft:
fix, new feature → feat,dependency bump → chore, etc.). State your reasoning in one line.
by the user's hint if one was given. Use American English unless --british was passed.
Do not describe how (the diff already shows that). Use the same language as the subject.
--breaking was passed, append ! to type/scope and add aBREAKING CHANGE: <explanation> footer.
--closes N or --refs N were passed, add the corresponding footers.--credit was passed, append Co-Authored-By: Claude Sonnet 4.6 <[email protected]>.Show the full proposed message in a code block. Ask the user to approve, edit, or cancel. Do not proceed until the user approves.
--staged)git add -u or specific files if theuser narrowed the scope during review).
git commit -m "$(cat <<'EOF'\n<message>\nEOF\n)" using a heredoc to preserveformatting. Pass --amend if --amend flag was given.
Diagnose the error, fix the underlying issue, and create a fresh commit.
git push. If the branch has no upstream, suggest git push -u origin <branch> andask before running it.
git log --oneline -1).message and wait for explicit confirmation.
git add -u orexplicit file paths.
user that this will require a force-push.
main or master.an empty commit.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.