Loading...
Loading...
Use when designing or writing a new package, procedure, function or trigger, or restructuring one - "viet package", "tao procedure", "them function", "them trigger", an API another team will call, an error-handling or logging design, a spec change. Applies the industry-standard PL/SQL design rules - the spec as a contract, named exceptions, one transaction owner, thin triggers - beneath the house conventions, which always win.
npx skill4agent add thaildhe172591/pythia pythia-packagepythia-write.pythia/conventions.mdreference/plsql-standards.mdTHE SPEC IS A CONTRACT: DESIGN IT FIRST, AND NEVER BREAK IT SILENTLYpythia similar <NAME>pythia srcpythia argspythia impact <PKG>pythia colspythia-spec%TYPEINOUTNOCOPYIN OUTOUT-20xxxDBMS_APPLICATION_INFO.SET_MODULE/SET_ACTIONAUTHID DEFINERACCESSIBLE BYDBMS_ASSERT/pythia unistrreference/plsql-standards.mdpythia-commentCOMMITpythia lint spec.sql body.sqlpythia-reviewpythia deploy spec.sql body.sqlpythia applypythia errors <PKG>pythia invalidpythia plscope <PKG>| Thought | Reality |
|---|---|
| "I'll just add a parameter to the existing procedure" | Every caller breaks or recompiles. Add an overload or a new unit at the end of the spec. |
| "WHEN OTHERS THEN log; is enough" | Without |
| "COMMIT at the end to be safe" | Now nobody can call it inside their transaction. The caller owns the commit. |
| "The trigger is the easiest place for this rule" | And the hardest to find, test and bypass for a data fix. API package. |
| "PRAGMA AUTONOMOUS_TRANSACTION fixes the mutating table" | It hides the error and reads stale data. Compound trigger. |
| "Concatenating the table name is fine, it's internal" | Internal today. |
| "Standards say X, the codebase does Y" | The codebase wins; propose X separately. |
pythia-writepythia-tablepythia-tunepythia-review