← ClaudeAtlas

pythia-deploylisted

Use when a change spans more than one statement or file - a release or migration script, "chay script DDL", "deploy ban release", "run these .sql files", a table with its comments and indexes, a package spec and body together, a directory of numbered scripts. Orders the statements, previews every one, gets one approval for the set, runs them through apply's six steps in order and stops at the first failure.
thaildhe172591/pythia · ★ 4 · AI & Automation · score 77
Install: claude install-skill thaildhe172591/pythia
# Deploying a Release **Announce at start:** "Using pythia-deploy — previewing every statement in the release first." **Phase:** Ask → Do — the whole ordered set is previewed and approved once, then run step by step A release script run with `sqlplus @release.sql` has no snapshot, no preview, no verify and no record of what landed before line 212 failed. `pythia deploy` runs the same file through the write path, statement by statement, so a failure stops cleanly with an exact list of what landed and how to undo it. ## The Iron Law ``` A RELEASE RUNS IN ORDER, AS PREVIEWED, AND STOPS AT THE FIRST BROKEN STEP ``` ## How a script is read - One statement per `;` for SQL; PL/SQL units (`CREATE ... PROCEDURE / FUNCTION / PACKAGE / TRIGGER / TYPE`) end at a line holding only `/`. A `;` or `/` inside a literal or a comment is text. - SQL*Plus directives (`SET`, `PROMPT`, `SPOOL`, `SHOW ERRORS`, `WHENEVER`, `DEFINE`, …) run nothing on the database: they are skipped and listed. - `@file` / `@@file` includes are **refused** — list the files instead; deploy never runs a path nobody looked at. - Refused, never skipped: anonymous `BEGIN ... END;` blocks (as in `apply`), `EXEC` / `HOST` / `CONNECT`, and `ALTER SESSION` — it would silently change how every later statement runs, which no preview can show. - Files run in the order given. A directory runs in natural name order when every file is numbered (`1_`, `02_`, `10_`, Flyway's `V3__`), otherwise by what each file c