← ClaudeAtlas

pythia-verifylisted

Use before saying an Oracle task is done, fixed, deployed, faster or working - before the final report, before "xong roi", "da sua xong", "deployed", before ending an autopilot session. Collects the evidence from this session - compile errors, INVALID objects against the baseline, lint, journal entries, before/after plans when performance was the point - and reports only what that evidence proves.
thaildhe172591/pythia · ★ 4 · AI & Automation · score 77
Install: claude install-skill thaildhe172591/pythia
# Verifying Before Claiming Done **Announce at start:** "Using pythia-verify — checking the evidence before I report." **Phase:** Learn → Ask — collect proof from the live database, then report what it shows and what it does not The most expensive sentence an agent writes is "done" about something that is not. In Oracle it is easy to say: a package can be written and INVALID, a release can stop at statement 7 of 12, a "faster" query can have the same plan. The evidence is three commands away — run them. ## The Iron Law ``` NO COMPLETION CLAIM WITHOUT EVIDENCE FROM THIS SESSION ``` Evidence is command output you saw after the last change, not a result you remember from before it. ## The Checklist 1. **Every write's verdict** — the exit code of each `apply` / `deploy`, read unpiped (`| tail` returns tail's 0). Under autopilot: `pythia autopilot report`, every row. 2. **It compiles** — `pythia errors <OBJECT>` for every object you touched: empty, or the errors listed. 3. **Nothing else broke** — `pythia invalid` compared with the baseline you took in `pythia-impact`. Anything INVALID now that was VALID then is yours until proven otherwise. 4. **It meets the standard** — `pythia lint <files>`: zero errors; warnings fixed or named with a reason. 5. **Tables are documented** — `pythia cols T` matches the spec; `pythia comments T` says 0 missing; `pythia stats T` lists no unindexed foreign key you created. 6. **Performance claims** — the same `pythia