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.
Create a git commit with all modified code and push to the remote repository.
Run git status to see what files have changed. Stage the relevant changes:
git add <file> for specific files or git add -A if all changes should be committedIf amending:
git commit --amend -m "<message>"git commit --amend --no-edit to keep the previous messageOtherwise:
git diff --cached to see what's staged, then draft a concise commit messagePush to the remote. If amending, use git push --force-with-lease. If no upstream exists, add -u origin <branch-name>. Both flags can be combined if needed.
Check if a PR already exists for this branch: gh pr view --json url 2>/dev/null
gh pr create --draft --title "<title>" --body "<body>"--force unless explicitly requested--no-verify) unless explicitly requestedgh repo fork --remote=true), then push to the fork and open a PR against the upstream repo~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.