@oriro/orirocli 0.1.9 → 0.1.12

package/skills/graphify/affected.py

@@ -1,154 +0,0 @@
-from __future__ import annotations
-
-from collections import deque
-from dataclasses import dataclass
-from pathlib import Path
-from typing import Iterable
-
-import networkx as nx
-
-
-DEFAULT_AFFECTED_RELATIONS = (
-    "calls",
-    "references",
-    "imports",
-    "imports_from",
-    "re_exports",
-    "inherits",
-    "extends",
-    "implements",
-    "uses",
-    "mixes_in",
-    "embeds",
-)
-
-
-@dataclass(frozen=True)
-class AffectedHit:
-    node_id: str
-    depth: int
-    via_relation: str
-
-
-def _node_label(graph: nx.Graph, node_id: str) -> str:
-    data = graph.nodes[node_id]
-    return str(data.get("label") or node_id)
-
-
-def _format_location(data: dict) -> str:
-    source_file = data.get("source_file") or "-"
-    source_location = data.get("source_location")
-    if source_location:
-        return f"{source_file}:{source_location}"
-    return str(source_file)
-
-
-def resolve_seed(graph: nx.Graph, query: str) -> str | None:
-    if query in graph:
-        return query
-    query_lower = query.lower()
-    exact_label_matches = [
-        str(node_id)
-        for node_id, data in graph.nodes(data=True)
-        if str(data.get("label", "")).lower() == query_lower
-    ]
-    if len(exact_label_matches) == 1:
-        return exact_label_matches[0]
-    exact_source_matches = [
-        str(node_id)
-        for node_id, data in graph.nodes(data=True)
-        if str(data.get("source_file", "")).lower() == query_lower
-    ]
-    if len(exact_source_matches) == 1:
-        return exact_source_matches[0]
-    contains_matches = [
-        str(node_id)
-        for node_id, data in graph.nodes(data=True)
-        if query_lower in str(data.get("label", "")).lower()
-    ]
-    if len(contains_matches) == 1:
-        return contains_matches[0]
-    return None
-
-
-def affected_nodes(
-    graph: nx.Graph,
-    seed: str,
-    *,
-    relations: Iterable[str] = DEFAULT_AFFECTED_RELATIONS,
-    depth: int = 2,
-) -> list[AffectedHit]:
-    relation_set = set(relations)
-    seen = {seed}
-    queue: deque[tuple[str, int]] = deque([(seed, 0)])
-    hits: list[AffectedHit] = []
-
-    while queue:
-        current, current_depth = queue.popleft()
-        if current_depth >= depth:
-            continue
-        if hasattr(graph, "in_edges"):
-            incoming = graph.in_edges(current, data=True)
-        else:
-            incoming = (
-                (source, target, data)
-                for source, target, data in graph.edges(data=True)
-                if target == current
-            )
-        for source, _target, data in incoming:
-            relation = str(data.get("relation", ""))
-            if relation not in relation_set:
-                continue
-            source = str(source)
-            if source in seen:
-                continue
-            seen.add(source)
-            hit = AffectedHit(source, current_depth + 1, relation)
-            hits.append(hit)
-            queue.append((source, current_depth + 1))
-
-    return hits
-
-
-def format_affected(
-    graph: nx.Graph,
-    query: str,
-    *,
-    relations: Iterable[str] = DEFAULT_AFFECTED_RELATIONS,
-    depth: int = 2,
-) -> str:
-    relation_list = tuple(relations)
-    seed = resolve_seed(graph, query)
-    if seed is None:
-        return f"No unique node match for {query}"
-
-    hits = affected_nodes(graph, seed, relations=relation_list, depth=depth)
-    lines = [
-        f"Affected nodes for {_node_label(graph, seed)}",
-        f"Relations: {', '.join(relation_list)}",
-        f"Depth: {depth}",
-    ]
-    if not hits:
-        lines.append("No affected nodes found.")
-        return "\n".join(lines)
-
-    for hit in hits:
-        data = graph.nodes[hit.node_id]
-        lines.append(
-            f"- {_node_label(graph, hit.node_id)} [{hit.via_relation}] {_format_location(data)}"
-        )
-    return "\n".join(lines)
-
-
-def load_graph(path: Path) -> nx.Graph:
-    import json
-    from networkx.readwrite import json_graph
-
-    raw = json.loads(path.read_text(encoding="utf-8"))
-    # Force directed so stored caller→callee direction survives the round-trip;
-    # mirrors serve.py and __main__.py (#1174).
-    raw = {**raw, "directed": True}
-    try:
-        return json_graph.node_link_graph(raw, edges="links")
-    except TypeError:
-        return json_graph.node_link_graph(raw)

package/skills/graphify/always_on/agents-md.md

@@ -1,12 +0,0 @@
-## graphify
-
-This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
-
-When the user types `/graphify`, invoke the `skill` tool with `skill: "graphify"` before doing anything else.
-
-Rules:
-- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
-- Dirty graphify-out/ files are expected after hooks or incremental updates; dirty graph files are not a reason to skip graphify. Only skip graphify if the task is about stale or incorrect graph output, or the user explicitly says not to use it.
-- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
-- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
-- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).

package/skills/graphify/always_on/antigravity-rules.md

@@ -1,14 +0,0 @@
----
-trigger: always_on
-description: Consult the graphify knowledge graph at graphify-out/ for codebase and architecture questions.
----
-
-## graphify
-
-This project has a graphify knowledge graph at graphify-out/.
-
-Rules:
-- For codebase or architecture questions, when `graphify-out/graph.json` exists, first run `graphify query "<question>"` (CLI) or `query_graph` (MCP). Use `graphify path "<A>" "<B>"` / `shortest_path` for relationships and `graphify explain "<concept>"` / `get_node` for focused concepts. These return a scoped subgraph, usually much smaller than `GRAPH_REPORT.md` or raw grep output.
-- If graphify-out/wiki/index.md exists, navigate it instead of reading raw files
-- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context
-- After modifying code files in this session, run `graphify update .` to keep the graph current (AST-only, no API cost)

package/skills/graphify/always_on/claude-md.md

@@ -1,9 +0,0 @@
-## graphify
-
-This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
-
-Rules:
-- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
-- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
-- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
-- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).

package/skills/graphify/always_on/gemini-md.md

@@ -1,9 +0,0 @@
-## graphify
-
-This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
-
-Rules:
-- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
-- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
-- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
-- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).

package/skills/graphify/always_on/kiro-steering.md

@@ -1,5 +0,0 @@
----
-inclusion: always
----
-
-graphify: A knowledge graph of this project lives in `graphify-out/`. For codebase, architecture, or dependency questions, when `graphify-out/graph.json` exists, first run `graphify query "<question>"` (or `graphify path "<A>" "<B>"` / `graphify explain "<concept>"`). These return a scoped subgraph, usually much smaller than `GRAPH_REPORT.md` or raw grep output. Read `GRAPH_REPORT.md` only for broad architecture review or when those commands do not surface enough context.

package/skills/graphify/always_on/vscode-instructions.md

@@ -1,17 +0,0 @@
-## graphify
-
-For any question about this repo's architecture, structure, components, or how to add/modify/find
-code, your first action should be `graphify query "<question>"` when `graphify-out/graph.json`
-exists. Use `graphify path "<A>" "<B>"` for relationship questions and `graphify explain "<concept>"`
-for focused-concept questions. These return a scoped subgraph, usually much smaller than the full
-report or raw grep output.
-
-Triggers: "how do I…", "where is…", "what does … do", "add/modify a <component>",
-"explain the architecture", or anything that depends on how files or classes relate.
-
-If `graphify-out/wiki/index.md` exists, use it for broad navigation. Read `graphify-out/GRAPH_REPORT.md`
-only for broad architecture review or when query/path/explain do not surface enough context. Only read
-source files when (a) modifying/debugging specific code, (b) the graph lacks the needed detail, or
-(c) the graph is missing or stale.
-
-Type `/graphify` in Copilot Chat to build or update the graph.