pythia-plsql 0.15.9__tar.gz → 0.15.11__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (68) hide show
  1. {pythia_plsql-0.15.9/scripts/pythia_plsql.egg-info → pythia_plsql-0.15.11}/PKG-INFO +24 -7
  2. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/README.md +22 -5
  3. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/pyproject.toml +4 -3
  4. pythia_plsql-0.15.11/queries/dba-dependencies-readable.sql +9 -0
  5. pythia_plsql-0.15.11/queries/synonyms-for.sql +13 -0
  6. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/scripts/pythia.py +356 -61
  7. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11/scripts/pythia_plsql.egg-info}/PKG-INFO +24 -7
  8. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/scripts/pythia_plsql.egg-info/SOURCES.txt +2 -0
  9. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-apply/SKILL.md +1 -1
  10. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-impact/SKILL.md +13 -0
  11. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-setup/SKILL.md +3 -0
  12. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/tests/test_install.py +16 -0
  13. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/tests/test_phase1.py +154 -0
  14. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/tests/test_phase3.py +82 -0
  15. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/tests/test_phase5.py +15 -0
  16. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/tests/test_phase6.py +189 -0
  17. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/LICENSE +0 -0
  18. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/comment-current.sql +0 -0
  19. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/compile-errors.sql +0 -0
  20. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/current-schema.sql +0 -0
  21. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/db-nls.sql +0 -0
  22. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/db-version.sql +0 -0
  23. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/dependencies.sql +0 -0
  24. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/explain-display.sql +0 -0
  25. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/impact.sql +0 -0
  26. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/invalid-objects.sql +0 -0
  27. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/name-occupants.sql +0 -0
  28. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/object-names.sql +0 -0
  29. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/object-source.sql +0 -0
  30. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/plscope-enabled.sql +0 -0
  31. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/plscope-statements.sql +0 -0
  32. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/plscope-usages.sql +0 -0
  33. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/schema-settings.sql +0 -0
  34. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/session-privileges.sql +0 -0
  35. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/similar-candidates.sql +0 -0
  36. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/source.sql +0 -0
  37. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/table-comments.sql +0 -0
  38. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/table-indexes.sql +0 -0
  39. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/table-stats.sql +0 -0
  40. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/queries/unindexed-fks.sql +0 -0
  41. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/scripts/pythia_plsql.egg-info/dependency_links.txt +0 -0
  42. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/scripts/pythia_plsql.egg-info/entry_points.txt +0 -0
  43. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/scripts/pythia_plsql.egg-info/requires.txt +0 -0
  44. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/scripts/pythia_plsql.egg-info/top_level.txt +0 -0
  45. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/setup.cfg +0 -0
  46. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-autopilot/SKILL.md +0 -0
  47. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-comment/SKILL.md +0 -0
  48. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-conventions/SKILL.md +0 -0
  49. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-deploy/SKILL.md +0 -0
  50. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-explore/SKILL.md +0 -0
  51. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-explore/reference/data-dictionary.md +0 -0
  52. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-package/SKILL.md +0 -0
  53. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-package/reference/plsql-standards.md +0 -0
  54. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-review/SKILL.md +0 -0
  55. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-review/reference/antipatterns.md +0 -0
  56. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-setup/reference/environment.md +0 -0
  57. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-skill-author/SKILL.md +0 -0
  58. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-spec/SKILL.md +0 -0
  59. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-table/SKILL.md +0 -0
  60. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-table/reference/ddl-standards.md +0 -0
  61. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-tune/SKILL.md +0 -0
  62. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-tune/reference/tuning-checklist.md +0 -0
  63. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-verify/SKILL.md +0 -0
  64. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-write/SKILL.md +0 -0
  65. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/pythia-write/reference/patterns.md +0 -0
  66. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/skills/using-pythia/SKILL.md +0 -0
  67. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/tests/test_mcp.py +0 -0
  68. {pythia_plsql-0.15.9 → pythia_plsql-0.15.11}/tests/test_phase2.py +0 -0
@@ -1,8 +1,8 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: pythia-plsql
3
- Version: 0.15.9
3
+ Version: 0.15.11
4
4
  Summary: PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback.
5
- License: MIT
5
+ License-Expression: MIT
6
6
  Project-URL: Homepage, https://github.com/thaildhe172591/pythia
7
7
  Project-URL: Repository, https://github.com/thaildhe172591/pythia
8
8
  Keywords: oracle,plsql,database,agent-skills,sql
@@ -27,7 +27,7 @@ Dynamic: license-file
27
27
  ![python](https://img.shields.io/badge/python-3.9%2B-blue)
28
28
 
29
29
  An Agent Skills + CLI kit for developing PL/SQL on Oracle Database with AI
30
- coding agents (Claude Code, Codex, Cursor — any of the 76 agents `npx skills`
30
+ coding agents (Claude Code, Codex, Cursor — any of the 70+ agents `npx skills`
31
31
  supports).
32
32
 
33
33
  pythia is a **harness**: a book of working rules an agent studies and follows
@@ -147,7 +147,7 @@ pythia check # fill in connections.json first, then verify
147
147
  ```
148
148
 
149
149
  The pip package is the whole kit: with Node.js present, `pythia install`
150
- runs `npx skills add` (77 agents, symlinked updates; `--source <git-url>`
150
+ runs `npx skills add` (70+ agents, symlinked updates; `--source <git-url>`
151
151
  for internal mirrors) — without Node it copies the bundled pack itself.
152
152
  Prefer **global skills**: `pythia install -g` once per machine serves every
153
153
  project, and per-project installs then skip the skills step automatically —
@@ -240,6 +240,18 @@ each agent needs you to finish by hand.
240
240
  Those are your permission preferences, so pythia does not set them for you
241
241
  ([why](GUIDE.md#11-optional-claude-code-permission-settings)).
242
242
 
243
+ **Installed as a plugin on Windows?** The plugin's hooks start through
244
+ `scripts/pythia-hook.sh`, which tries the `py` launcher, then `python3`,
245
+ then `python`, and skips the Microsoft Store alias — a bare `python` on a
246
+ fresh Windows machine is often that alias, or not on PATH at all. When none
247
+ runs, the guard blocks Bash and says why instead of failing open. The
248
+ plugin's MCP server still starts with `python`; `pythia doctor` checks it,
249
+ and the plugin's own hooks and version, and names the fix: add
250
+ `%LOCALAPPDATA%\Programs\Python\Python3xx\` to PATH (or reinstall Python with
251
+ "Add python.exe to PATH"), turn off the python.exe App execution aliases,
252
+ restart Claude Code. With the plugin on, do not also run `pythia install`
253
+ for the hooks — doctor counts what the plugin provides.
254
+
243
255
  **Approving a change:** the agent previews with `pythia apply`, asks an
244
256
  `AskUserQuestion` carrying the card, you click **Approve**, and the agent runs
245
257
  `apply --confirm` itself. If that dialog's answer does not count (it closed
@@ -376,9 +388,14 @@ The skills teach the agent the workflow — gates, not suggestions:
376
388
  | | |
377
389
  |---|---|
378
390
  | OS | Windows, macOS, Linux, WSL — full test matrix in CI |
379
- | Python | 3.9+ · stdlib + `python-oracledb` (thin mode) only |
380
- | Oracle | core works broadly; PL/Scope statement capture needs 12.2+; license-safe views only |
381
- | Agents | any `npx skills` agent (76) · native Claude Code plugin (hooks + MCP approver, any permission mode but `dontAsk`) · Codex (AGENTS.md harness + MCP approver, ≥ v0.120 for chat-style approval) |
391
+ | Python | 3.9+ · stdlib + `python-oracledb` only — thin mode by default, thick mode when the database needs it |
392
+ | Oracle | 12.1 to 23ai in thin mode, with no Oracle Client; 10.2 and 11.2, accounts with an old 10G password verifier, and servers that require Native Network Encryption through thick mode, which pythia switches to by itself when an Oracle Client is installed (GUIDE §2) · PL/Scope statement capture needs 12.2+; license-safe views only |
393
+ | Agents | any `npx skills` agent (70+) · native Claude Code plugin (hooks + MCP approver, any permission mode but `dontAsk`) · Codex (AGENTS.md harness + MCP approver, ≥ v0.120 for chat-style approval) |
394
+
395
+ ## Who is using pythia
396
+
397
+ Nobody is listed yet. Using pythia on a real codebase? Open a pull request
398
+ that adds a line here: your team or project, and what you use pythia for.
382
399
 
383
400
  ## Star History
384
401
 
@@ -13,7 +13,7 @@
13
13
  ![python](https://img.shields.io/badge/python-3.9%2B-blue)
14
14
 
15
15
  An Agent Skills + CLI kit for developing PL/SQL on Oracle Database with AI
16
- coding agents (Claude Code, Codex, Cursor — any of the 76 agents `npx skills`
16
+ coding agents (Claude Code, Codex, Cursor — any of the 70+ agents `npx skills`
17
17
  supports).
18
18
 
19
19
  pythia is a **harness**: a book of working rules an agent studies and follows
@@ -133,7 +133,7 @@ pythia check # fill in connections.json first, then verify
133
133
  ```
134
134
 
135
135
  The pip package is the whole kit: with Node.js present, `pythia install`
136
- runs `npx skills add` (77 agents, symlinked updates; `--source <git-url>`
136
+ runs `npx skills add` (70+ agents, symlinked updates; `--source <git-url>`
137
137
  for internal mirrors) — without Node it copies the bundled pack itself.
138
138
  Prefer **global skills**: `pythia install -g` once per machine serves every
139
139
  project, and per-project installs then skip the skills step automatically —
@@ -226,6 +226,18 @@ each agent needs you to finish by hand.
226
226
  Those are your permission preferences, so pythia does not set them for you
227
227
  ([why](GUIDE.md#11-optional-claude-code-permission-settings)).
228
228
 
229
+ **Installed as a plugin on Windows?** The plugin's hooks start through
230
+ `scripts/pythia-hook.sh`, which tries the `py` launcher, then `python3`,
231
+ then `python`, and skips the Microsoft Store alias — a bare `python` on a
232
+ fresh Windows machine is often that alias, or not on PATH at all. When none
233
+ runs, the guard blocks Bash and says why instead of failing open. The
234
+ plugin's MCP server still starts with `python`; `pythia doctor` checks it,
235
+ and the plugin's own hooks and version, and names the fix: add
236
+ `%LOCALAPPDATA%\Programs\Python\Python3xx\` to PATH (or reinstall Python with
237
+ "Add python.exe to PATH"), turn off the python.exe App execution aliases,
238
+ restart Claude Code. With the plugin on, do not also run `pythia install`
239
+ for the hooks — doctor counts what the plugin provides.
240
+
229
241
  **Approving a change:** the agent previews with `pythia apply`, asks an
230
242
  `AskUserQuestion` carrying the card, you click **Approve**, and the agent runs
231
243
  `apply --confirm` itself. If that dialog's answer does not count (it closed
@@ -362,9 +374,14 @@ The skills teach the agent the workflow — gates, not suggestions:
362
374
  | | |
363
375
  |---|---|
364
376
  | OS | Windows, macOS, Linux, WSL — full test matrix in CI |
365
- | Python | 3.9+ · stdlib + `python-oracledb` (thin mode) only |
366
- | Oracle | core works broadly; PL/Scope statement capture needs 12.2+; license-safe views only |
367
- | Agents | any `npx skills` agent (76) · native Claude Code plugin (hooks + MCP approver, any permission mode but `dontAsk`) · Codex (AGENTS.md harness + MCP approver, ≥ v0.120 for chat-style approval) |
377
+ | Python | 3.9+ · stdlib + `python-oracledb` only — thin mode by default, thick mode when the database needs it |
378
+ | Oracle | 12.1 to 23ai in thin mode, with no Oracle Client; 10.2 and 11.2, accounts with an old 10G password verifier, and servers that require Native Network Encryption through thick mode, which pythia switches to by itself when an Oracle Client is installed (GUIDE §2) · PL/Scope statement capture needs 12.2+; license-safe views only |
379
+ | Agents | any `npx skills` agent (70+) · native Claude Code plugin (hooks + MCP approver, any permission mode but `dontAsk`) · Codex (AGENTS.md harness + MCP approver, ≥ v0.120 for chat-style approval) |
380
+
381
+ ## Who is using pythia
382
+
383
+ Nobody is listed yet. Using pythia on a real codebase? Open a pull request
384
+ that adds a line here: your team or project, and what you use pythia for.
368
385
 
369
386
  ## Star History
370
387
 
@@ -1,13 +1,14 @@
1
1
  [build-system]
2
- requires = ["setuptools>=64"]
2
+ requires = ["setuptools>=77"]
3
3
  build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "pythia-plsql"
7
- version = "0.15.9"
7
+ version = "0.15.11"
8
8
  description = "PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback."
9
9
  readme = "README.md"
10
- license = { text = "MIT" }
10
+ license = "MIT"
11
+ license-files = ["LICENSE"]
11
12
  requires-python = ">=3.9"
12
13
  dependencies = ["oracledb>=2.0"]
13
14
  keywords = ["oracle", "plsql", "database", "agent-skills", "sql"]
@@ -0,0 +1,9 @@
1
+ -- Purpose: probe whether this session can read DBA_DEPENDENCIES. When it
2
+ -- cannot (ORA-00942), ALL_DEPENDENCIES lists only dependents the
3
+ -- session has access to, so impact says other schemas may hide
4
+ -- some. One row at most: the answer is "readable", not a count.
5
+ -- Binds: (none)
6
+ -- Returns: N (1 when any dependency row exists)
7
+ select count(*) n
8
+ from dba_dependencies
9
+ where rownum = 1
@@ -0,0 +1,13 @@
1
+ -- Purpose: the synonyms that point straight at an object — other names a
2
+ -- caller can reach it by, which neither ALL_DEPENDENCIES' tree nor
3
+ -- a grep for the object's own name will show. Direct synonyms
4
+ -- only: a synonym of a synonym is not followed.
5
+ -- Binds: :s schema (owner of the object)
6
+ -- :n object name
7
+ -- Returns: OWNER, SYNONYM_NAME (PUBLIC for a public synonym)
8
+ select s.owner,
9
+ s.synonym_name
10
+ from all_synonyms s
11
+ where s.table_owner = :s
12
+ and s.table_name = upper(:n)
13
+ order by case s.owner when 'PUBLIC' then 0 else 1 end, s.owner, s.synonym_name