fix-the-root-cause — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited fix-the-root-cause (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.
The place a bug shows up is rarely the place it comes from. Patching the symptom at the surface leaves the real cause free to break something else next week. Find the layer that produced the bad state and fix it there.
Any bug fix, especially a crash, a null, a corrupt value, or a wrong result that shows up far from where the data was created.
Trace the bad value back to where it was born, not just where it blew up. Ask "what let this state exist in the first place?" and fix that.
A guard at the call site is fine as a seatbelt, but it isn't the fix if something upstream keeps handing out broken state.
A page crashes on user.address.city because address is null. The symptom fix is a null check on the page. But the real cause is the user loader, which returns a half-built user when a join fails, so any page that touches address is one click from the same crash. Fixing the loader to either return a complete user or fail loudly kills the whole class of crashes. The null check alone just moves the next crash to a different page.
| Thought | Reality |
|---|---|
| "A null check here makes it stop crashing" | It stops this crash, not the cause. |
| "The bug is on this page" | The bug is wherever the bad value was made. |
| "I'll patch the symptom now and fix it properly later" | Later rarely comes, and the bad state keeps spreading. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.