← ClaudeAtlas

pythia-impactlisted

Use before proposing or writing any change to an Oracle object - a procedure, package, function, trigger, view, or table. Impact analysis comes first, because what depends on an object decides how careful the change must be, and Oracle invalidates dependents in cascade.
thaildhe172591/pythia · ★ 4 · AI & Automation · score 77
Install: claude install-skill thaildhe172591/pythia
# Impact Before Change **Announce at start:** "Using pythia-impact to measure the blast radius first." **Phase:** Learn — and the first Ask gate: a large blast radius reaches the developer before any code is written Changing an Oracle object recompiles or invalidates everything that depends on it — immediately, schema-wide, for every user of a shared database. The cost of knowing first is one command. ## The Iron Law ``` NO CHANGE PROPOSED WITHOUT ITS IMPACT MEASURED FIRST ``` ## The Workflow 1. `pythia impact <OBJECT> --depth 2` — everything that depends on it, as a tree, ending with the line that matters: `-- impact: N dependent objects, M currently VALID`. Up to three more `--` lines follow, and each one is a reason the tree can be smaller than the truth — relay them, never call the list complete while one is printed: - `-- also reachable as: PUBLIC.ORDERS, ... (synonyms)` — callers can use those names too; grep for them as well as the object's own name. - `-- not shown: references inside dynamic SQL strings. Check with: pythia grep <OBJECT>` — `EXECUTE IMMEDIATE` and `DBMS_SQL` record no dependency. Run the printed command; it is always printed, even after "nothing depends on". - `-- other schemas: only dependents this session can see are listed` — this session cannot read `DBA_DEPENDENCIES`, so a schema that granted it nothing can still depend on the object. Say so when the change matters outside the schem