apw-commit — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited apw-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.
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.
Use this skill when the user wants to commit (and optionally push) pending changes. Follow every step below in order.
Run the following commands to understand what will be committed:
git status
git diff HEADIf there are no changes (clean working tree and staging area), tell the user there is nothing to commit and stop.
Look for the file .claude/skills/apw-commit/COMMIT_SCHEMA.md in the repository root.
If it exists: read it and use it as the authoritative format guide for all commit messages in this project. Proceed to Step 3.
If it does not exist:
Suggested commit message schema:
<type>(<scope>): <short summary>
<body — what changed and why, optional>
<footer — breaking changes, issue refs, co-authors, optional>Types: feat, fix, refactor, chore, docs, test, style, perf
Rules:
Closes #123.claude/skills/apw-commit/COMMIT_SCHEMA.md so it is used automatically in future runs.Using the schema from Step 2 as the format guide and the diff from Step 1 as the content source:
Show the user:
git status)Then ask: "Commit these changes? Also push to remote? (yes/no/yes+push)"
Wait for explicit confirmation before proceeding. Do not commit without it.
Staging: Stage only the files that are relevant to the changes being committed. Prefer git add <specific-files> over git add -A unless the user explicitly wants to stage everything.
Committing: Use a HEREDOC to pass the multi-line commit message:
git commit -m "$(cat <<'EOF'
<subject line>
<body>
<footer>
EOF
)"Pushing: If the user asked to push, run git push after a successful commit. Confirm the target remote and branch before pushing (e.g., origin main). Do not force-push unless the user explicitly requests it.
After each operation run git status to verify the outcome and report it to the user.
Tell the user:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.