commit-push-pr — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited commit-push-pr (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.
Gather this context first:
git statusgit diff HEADgit branch --show-currentgit diff main...HEAD (or default branch)gh pr view --json number 2>/dev/null || trueAnalyze ALL changes that will be included in the pull request - look at ALL commits from git diff main...HEAD, not just the latest commit.
Based on the changes:
Use the format username/feature-name:
git checkout -b username/descriptive-feature-nameUse heredoc syntax for the message:
git commit -m "$(cat <<'EOF'
Commit message here.
EOF
)"git log --oneline -10)git push -u origin HEADCheck if a PR already exists (from the gh pr view output above).
If PR exists - update it:
gh pr edit --title "Short title" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>
## Test plan
- [ ] Test item 1
- [ ] Test item 2
EOF
)"If no PR - create one:
gh pr create --title "Short, descriptive title" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>
## Test plan
- [ ] Test item 1
- [ ] Test item 2
EOF
)"Rules:
Do all of the above in a single message using multiple tool calls. Return the PR URL when done.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.