atomic-commit-and-push — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited atomic-commit-and-push (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.
Review staged + unstaged changes. Group by mechanism/file boundary. Create one commit per logical change. Run repo-native type-checker and linter before each commit. Do NOT bundle unrelated changes.
Prefer git submit when git-branchless is installed and the forge is supported. Fallback: pick a descriptive branch name, then git push origin HEAD:refs/heads/<branch>. Set upstream only when the user explicitly wants tracking. Never --force or --force-with-lease without explicit user authorization. Never push directly to protected branches (e.g., main, master, release/*).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.