rigorous-data-auditlisted
Install: claude install-skill willy92wins/DayZ-Modding-Knowledge-Pack
# Rigorous Data Audit
Procedure for auditing mods where a bug equals lost player progression. Built
from a real failure: six parallel Opus reasoning agents reviewed LF_VStorage
1.4.6 from independent angles and signed off as "release-safe" — an external
implementer-grade audit then found 12 VULNs (P0–P3) the agents missed. This
skill encodes the lessons.
A second failure refined it further: a loose application of this skill's
"parallel agents + consolidation" shape — pointed at fact-checking a corpus —
produced an audit that was **~55% confabulated**, because there was no
adversarial verification step between "agents reported it" and "acting on it".
Step 3 below exists because of that. See `postmortem.md` for the case.
Read `references/why-this-skill-exists.md` for the full retrospective if you
want the original case study.
## When to invoke
Trigger automatically when any of these are true:
- Mod touches persistence, save files, state machines, or async work queues
- A bug would cause **silent data loss** (lost items, wrong sids, money loss)
- User asks for "audit", "revisa a fondo", "release-safe?", "puede romper progresión"
- User just applied multiple fixes and wants verification before rebuild/test
- User hands you findings from an external auditor and asks you to verify
If the change is cosmetic or UI-only, this skill is overkill — skip it.
## Why reasoning alone is insufficient
The reasoning agents that signed off on LF_VStorage 1.4.6 were not lazy. Each
read t