← ClaudeAtlas

pythia-applylisted

Use when a PL/SQL change is ready to reach the database - applying a CREATE OR REPLACE, restoring from the journal, or any other write. Runs the six-step flow through pythia apply and enforces the gate - the developer sees the preview and approves in chat before anything is written, and a broken result is never reported as success.
thaildhe172591/pythia · ★ 4 · AI & Automation · score 77
Install: claude install-skill thaildhe172591/pythia
# Applying PL/SQL Changes **Announce at start:** "Using pythia-apply — I'll preview the change first." **Phase:** Ask → Do — the preview is relayed and approved before the one write door opens DDL in Oracle commits itself, so the snapshot pythia takes before writing is the only undo there is — for DML not even that. This skill is how it gets used. ## The Iron Law ``` NO WRITE THE DEVELOPER HAS NOT SEEN AND APPROVED ``` Every write: new objects, fixes, restores, batch runs. No exception for "trivial" — a one-line change can invalidate twelve dependents. Four moves are FORBIDDEN for agents, and pythia enforces all four (the CLI refuses without a terminal; the pre-tool hook denies the last): - `--yes` — it is the developer's flag, never yours. - Minting the approval. `pythia approve <token>` is the developer's console command; an agent cannot run it. Your door is to ASK (step 3): the grant is minted only from the developer's own answer. - `pythia policy set <group>` to anything LOOSER, and `pythia autopilot on` — the developer's decisions; hand them the exact command to run themselves. - Writing around the gate — sqlplus, SQLcl `run-sql`, a driver script. One move is yours: `--confirm` — only after `Approve`, or a console approve. **Exception: an active autopilot lease** (`pythia-autopilot`) the developer approved — then `pythia apply <file>` lands covered statements itself, and the preview says `autopilot: applying under lease`, or why it does not. ## When the c