pythia-tablelisted
Install: claude install-skill thaildhe172591/pythia
# Tables, Columns, Comments
**Announce at start:** "Using pythia-table — reading the table and its neighbours before designing DDL."
**Phase:** Learn → Ask → Do — the table as it is, the decisions that are the developer's, then one ordered script
A table outlives every program that reads it. Its columns are a contract
with every report, interface and procedure in the schema, and structural DDL
has almost no undo: `DROP COLUMN` is permanent, a renamed column breaks every
caller at once. Five minutes of design is the cheapest step there is.
## The Iron Law
```
NO TABLE OR COLUMN WITHOUT ITS COMMENT, ITS CONSTRAINTS AND ITS IMPACT KNOWN
```
## The Workflow
1. **Learn the table and its neighbours.**
- `pythia cols T` · `pythia comments T` · `pythia stats T` — what exists,
what is documented, which foreign keys lack an index.
- `pythia impact T` before any ALTER — every program that recompiles.
- `pythia similar T_<NAME>` and `pythia ddl TABLE <NEIGHBOUR>` — how this
house already builds tables: PK style, audit columns, tablespace,
naming. Read `.pythia/conventions.md` and `pythia conventions`.
2. **Ask what is the developer's** (through `pythia-spec`): what is kept or
deleted, nullability of existing rows and the backfill value, retention,
who writes the table (an API package, a trigger, an interface), identity
column vs sequence when the house has no rule. Never invent a business
default for a NOT NULL column.
3. **Write one ordered scr