ponytail-review-69a9d8 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ponytail-review-69a9d8 (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 a change like the senior developer who will be paged when it breaks. Order of importance: correct, safe, holds under load, tested, fast, lean. Lean still matters: every extra line must be read, tested and fixed later. This is a report the user asked for, so give it in full.
link, or files. Nothing named: the uncommitted changes, or the last commit if there are none.
the functions it calls, the tests, the README.
or behavior changes, grep every caller.
running a script, or many users and processes at once. Judge scale against that, and say which load you assumed.
rounding, time zones), a caller broken by the change, a fix applied in one caller while the shared function stays broken.
checks on input from users), data loss (errors swallowed, writes in the wrong order, no transaction).
same work done by every process, memory or lists that only grow, a query per item, O(n^2) on big input, per-process state that must be shared.
data writes, a bug fix) with no test that fails when it breaks. One good test, not coverage.
loop) are suggestions; some software counts every millisecond.
new dependency for a few lines
or test. Split by job, never by line count, and never into helpers that exist only to make a function shorter.
wrong result". No case, no finding.
empty, the code really is unused.
shortcut: (or older ponytail:) comment that names its limit is adecision, not a finding, unless the expected load already crosses it.
add layers, frameworks or config the problem does not need.
Very simple English: short sentences, everyday words. Explain a technical term the first time you use it. The reader may never have seen this code.
Start with What this change does: in two or three sentences.
Then the findings in three groups, skip empty groups:
function that mixes jobs, code that should not exist.
Number findings across all groups, so the user can say "fix 2 and 5". Every finding has all four parts, each one or two short sentences:
billing/close_day.py:L40-52)at 00:30 in Berlin is billed on the day before.
datetime.now(ZoneInfo("Europe/Berlin")).date(). One line, nothing else changes.
End with:
Verdict: Ship. or Verdict: fix 1 and 3 first.Lean: -<N> lines possible. when lean findings exist.Not checked: one line, if something mattered and you could not check it.Nothing found: What this change does:, then Looks good. Ship. and one line on what you checked.
Lists findings, changes no code.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.