← ClaudeAtlas

pythia-explorelisted

Use when you need to understand anything in an Oracle schema - finding objects, reading PL/SQL source, signatures, table columns, DDL, searching code, or asking who uses what. ALSO use when a .sql file, dump, export, migration script or repo copy of an object appears to answer the question already, including one the developer points you at - because those files drift from the database and are wrong in ways that read as correct. The database is the only source of truth.
thaildhe172591/pythia · ★ 4 · AI & Automation · score 77
Install: claude install-skill thaildhe172591/pythia
# Exploring the Schema **Announce at start:** "Using pythia-explore — asking the database directly." **Phase:** Learn ## The principle: ask the database, never the dump Repositories of exported `.sql` files go stale the day after export. A real mid-size system, audited in 2026, compared its repo dump against the live database: | Object type | In the dump | In the database | Verdict | |---|---|---|---| | Procedures | 3,827 | 3,827 | matched | | Tables | 952 | 952 | matched | | **Types** | **0** | **115** | **all missing** | | **Packages** | **0** | **9** | **all missing** | | **Indexes** | **116** | **1,016** | **~89% missing** | Code that "reads fine" against the dump can reference types and packages the dump never heard of. **When the developer hands you a `.sql` file** — "explain this procedure", "here is the export, what does it do" — the file is a claim, not the truth. Read it, then run `pythia src <NAME>` and answer from the database. If the two differ, say so first: which is newer is exactly what the developer needs to know, and it is invisible from the file alone. Never answer about a database object from a file alone while the database is reachable. Read files as the answer only when the database is unreachable — and say that is what you are doing. ## What you need → what you run | Need | Command | |---|---| | Is the connection alive, what schema | `pythia check` | | Find objects by name | `pythia ls "PKG_%"` | | Read source, with the compiler's line numbers