pythia-plsql 0.3.3__tar.gz → 0.3.5__tar.gz

{pythia_plsql-0.3.3/scripts/pythia_plsql.egg-info → pythia_plsql-0.3.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.3.3
+Version: 0.3.5
 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.
 License: MIT
 Project-URL: Homepage, https://github.com/thaildhe172591/pythia

{pythia_plsql-0.3.3 → pythia_plsql-0.3.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythia-plsql"
-version = "0.3.3"
+version = "0.3.5"
 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."
 readme = "README.md"
 license = { text = "MIT" }

{pythia_plsql-0.3.3 → pythia_plsql-0.3.5}/scripts/pythia.py

@@ -1659,20 +1659,26 @@ def global_pack_present(home=None):
 def copy_bundled_skills(base_dir):
     """No-Node fallback: copy the wheel-bundled pack into
     <base>/.claude/skills/ ONLY — the directory Claude Code reliably reads
-    in both scopes (field evidence: project .agents/skills is invisible to
-    some Claude Code versions, and a second copy doubles every menu entry).
-    base_dir is the project root, or the home directory for -g. The copy
-    merges: only the pack's own skills are refreshed; stale copies of the
-    pack under .agents/skills and old plsql-* names are cleaned."""
+    in both scopes (field evidence: a project's .agents/skills is invisible
+    to some Claude Code versions, and a second copy doubles every menu
+    entry). base_dir is the project root, or the home directory for -g.
+
+    Both destinations are cleared link-first before the copy. An earlier
+    `npx skills add` leaves .claude/skills/<name> as a symlink into
+    .agents/skills/<name>; copying into that symlink would write through to
+    its target, which the .agents cleanup then deletes — leaving a dangling
+    link and no pack at all. Only the pack's own names are touched; other
+    skills in those directories are left alone."""
     import shutil
-    dest_root = pathlib.Path(base_dir) / ".claude" / "skills"
+    base = pathlib.Path(base_dir)
+    dest_root = base / ".claude" / "skills"
     for pack in sorted(SKILLS_DIR.iterdir()):
         if not (pack / "SKILL.md").is_file():
             continue
-        shutil.copytree(pack, dest_root / pack.name, dirs_exist_ok=True)
+        _remove_link_first(dest_root / pack.name)
+        _remove_link_first(base / ".agents" / "skills" / pack.name)
+        shutil.copytree(pack, dest_root / pack.name)
     clean_legacy_skills(base_dir)
-    for name in pack_names():   # canonical copy lives in .claude now
-        _remove_link_first(pathlib.Path(base_dir) / ".agents" / "skills" / name)
     return [dest_root]
 
 

{pythia_plsql-0.3.3 → pythia_plsql-0.3.5/scripts/pythia_plsql.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.3.3
+Version: 0.3.5
 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.
 License: MIT
 Project-URL: Homepage, https://github.com/thaildhe172591/pythia

{pythia_plsql-0.3.3 → pythia_plsql-0.3.5}/skills/pythia-explore/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pythia-explore
-description: Use when you need to understand anything in an Oracle schema - finding objects, reading PL/SQL source, signatures, table columns, DDL, searching code, or asking who uses what. ALSO use when a .sql file, dump, export, migration script or repo copy of an object appears to answer the question already, including when the developer points you at one: those files drift from the database and are wrong in ways that read as correct. The database is the only source of truth.
+description: Use when you need to understand anything in an Oracle schema - finding objects, reading PL/SQL source, signatures, table columns, DDL, searching code, or asking who uses what. ALSO use when a .sql file, dump, export, migration script or repo copy of an object appears to answer the question already, including one the developer points you at - because those files drift from the database and are wrong in ways that read as correct. The database is the only source of truth.
 ---
 
 # Exploring the Schema

{pythia_plsql-0.3.3 → pythia_plsql-0.3.5}/tests/test_install.py

@@ -65,6 +65,29 @@ def test_missing_npx_falls_back_to_the_bundled_pack():
         pythia.copy_bundled_skills(td)                       # idempotent
 
 
+def test_copy_survives_a_symlinked_destination():
+    """`npx skills add` leaves .claude/skills/<name> as a symlink into
+    .agents/skills/<name>. Copying through that link and then cleaning the
+    target left dangling links and no pack — it happened on a real machine."""
+    with tempfile.TemporaryDirectory() as td:
+        base = pathlib.Path(td)
+        agents = base / ".agents" / "skills" / "pythia-explore"
+        claude = base / ".claude" / "skills"
+        agents.mkdir(parents=True)
+        (agents / "SKILL.md").write_text("old", encoding="utf-8")
+        claude.mkdir(parents=True)
+        try:
+            (claude / "pythia-explore").symlink_to(agents,
+                                                   target_is_directory=True)
+        except (OSError, NotImplementedError):
+            return          # no symlink privilege on this box; skip
+        pythia.copy_bundled_skills(td)
+        real = claude / "pythia-explore" / "SKILL.md"
+        assert real.is_file(), "pack vanished through the symlink"
+        assert not (claude / "pythia-explore").is_symlink()
+        assert "old" not in real.read_text(encoding="utf-8")
+
+
 def test_global_pack_detection_skips_project_copies():
     with tempfile.TemporaryDirectory() as home:
         assert not pythia.global_pack_present(home)

{pythia_plsql-0.3.3 → pythia_plsql-0.3.5}/tests/test_phase5.py

@@ -54,6 +54,33 @@ def test_frontmatter_is_valid_and_triggering():
         assert len(desc) <= 1024, f"{name}: description too long ({len(desc)})"
 
 
+def test_frontmatter_is_parseable_yaml():
+    """A description holding an unquoted ": " is not valid YAML, and the
+    agent harness then falls back to the H1 heading — the skill keeps its
+    name but loses its trigger, so it silently stops firing. This shipped
+    once; it does not ship twice. Checked without PyYAML: the suites run on
+    the stdlib alone.
+    """
+    for name in sorted(EXPECTED):
+        path = SKILLS / name / "SKILL.md"
+        if not path.is_file():
+            continue
+        m = re.match(r"^---\n(.*?)\n---\n", path.read_text(encoding="utf-8"),
+                     re.S)
+        assert m, f"{name}: no YAML frontmatter"
+        for line in m.group(1).splitlines():
+            km = re.match(r"^([A-Za-z_][\w.]*):\s+(.*)$", line)
+            if not km:
+                continue            # continuation or nested line
+            value = km.group(2)
+            if value[:1] in "\"'":
+                continue            # quoted: a colon inside is fine
+            assert ": " not in value, (
+                f"{name}: frontmatter '{km.group(1)}' holds an unquoted "
+                f"': ' — YAML reads that as a nested mapping and the field "
+                f"is lost. Rephrase or quote the value.")
+
+
 def test_skill_bodies_stay_within_budget():
     for name in sorted(EXPECTED):
         path = SKILLS / name / "SKILL.md"