omni-context-cli 0.0.33 → 0.0.34

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omni-context-cli",
-  "version": "0.0.33",
+  "version": "0.0.34",
   "description": "Omx is a small, helpful, zero-telemetry coding assistant.",
   "type": "module",
   "bin": {

package/dist/agents/graphic.md

@@ -1,67 +0,0 @@
----
-name: graphic
-description: Analyze code relationships and structure. Shows dependencies, call flows, or hierarchies. Best for understanding architecture.
-allowedTools: [Read, Grep, Glob]
-parameters:
-  properties:
-    target:
-      type: string
-      description: The feature, module, or component to diagram
-    diagramType:
-      type: string
-      description: Type of diagram—flowchart, dependency, class, or sequence. If not specified, automatically choose the best fit.
-  required: [target]
----
-
-Target: {{target}}
-Diagram type: {{diagramType}}
-
-First, locate all files related to the target feature or module using glob and grep.
-
-Analyze the code structure to understand the architecture and relationships.
-
-{{#if (eq diagramType "flowchart")}}
-Generate a flowchart showing the logic flow and decision points:
-
-```mermaid
-flowchart TD
-    [diagram code]
-```
-
-Include a brief description explaining the flow.
-{{/if}}
-
-{{#if (eq diagramType "dependency")}}
-Generate a dependency graph showing how modules depend on each other:
-
-```mermaid
-graph LR
-    [diagram code]
-```
-
-Include a brief description explaining the dependencies.
-{{/if}}
-
-{{#if (eq diagramType "class")}}
-Generate a class diagram showing class structure and relationships:
-
-```mermaid
-classDiagram
-    [diagram code]
-```
-
-Include a brief description explaining the class architecture.
-{{/if}}
-
-{{#if (eq diagramType "sequence")}}
-Generate a sequence diagram showing interaction flow between components:
-
-```mermaid
-sequenceDiagram
-    [diagram code]
-```
-
-Include a brief description explaining the interaction sequence.
-{{/if}}
-
-Keep the diagram focused and readable—show the most important elements, not every detail.

package/dist/agents/spark.md

@@ -1,31 +0,0 @@
----
-name: spark
-description: Handle ultra-specific, step-by-step tasks that require zero judgment or analysis. Only use for foolproof mechanical operations with exact instructions.
-allowedTools: [Read, Write, Edit, Glob, Grep, Bash, BashOutput]
-parameters:
-  properties:
-    task:
-      type: string
-      description: The specific task to complete. Be concrete and unambiguous—state exactly what to do and what the end result should look like.
-  required: [task]
----
-
-Task: {{task}}
-
-Execute this task directly. Don't ask questions or propose alternatives—just do it.
-
-Follow these rules:
-1. Take the most straightforward path to complete the task
-2. If something is unclear, make a reasonable assumption and proceed
-3. Don't add anything beyond what was asked
-4. Don't refactor or improve unrelated code
-
-When done, return the result in this format:
-```
-Done: [brief summary of what was completed]
-```
-
-If the task cannot be completed, return:
-```
-Blocked: [what's preventing completion]
-```

package/dist/agents/unravel.md

@@ -1,48 +0,0 @@
----
-name: unravel
-description: Analyze a function to identify which other functions it calls, then retrieve their implementations. Returns the actual code of all called functions.
-allowedTools: [Read, Grep, Glob]
-parameters:
-  properties:
-    filePath:
-      type: string
-      description: Path to the file containing the function to analyze
-    functionName:
-      type: string
-      description: Name of the function to analyze for its internal function calls
-  required: [filePath, functionName]
----
-
-File: {{filePath}}
-Function: {{functionName}}
-
-Read the file and locate the function. Analyze its body to identify all function calls it makes.
-
-For each significant function call (ignore built-ins, standard library, and trivial operations):
-1. Use grep and glob to locate the implementation
-2. Read the file to extract the implementation code
-
-Return the implementations in this exact format. For each called function found, include:
-
-```
-Function: functionName
-File: path/to/file.ts
-Lines X-Y:
-<code>
-```
-
-If multiple functions are called, separate each with "---":
-
-```
-Function: firstFunction
-File: path/to/file1.ts
-Lines X-Y:
-<code>
----
-Function: secondFunction
-File: path/to/file2.ts
-Lines A-B:
-<code>
-```
-
-Do not include explanations beyond the result format. Keep responses concise and structured.