omni-context-cli 0.0.81 → 0.0.83

package/dist/skills/simplify/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: simplify
-description: Review changed code for reuse, quality, and efficiency, then fix any issues found. Use when the user asks to review, clean up, or simplify recent code changes.
+description: Review changed code for reuse, quality, and efficiency, then fix any issues found.
 ---
 
 # Simplify: Code Review and Cleanup
@@ -17,9 +17,9 @@ Run `git diff` (or `git diff HEAD` if there are staged changes) to see what chan
 
 For each change:
 
-1. **Search for existing utilities and helpers** that could replace newly written code. Look for similar patterns elsewhere in the codebase -- common locations are utility directories, shared modules, and files adjacent to the changed ones.
+1. **Search for existing utilities and helpers** that could replace newly written code. Look for similar patterns elsewhere in the codebase. Common locations are utility directories, shared modules, and files adjacent to the changed ones.
 2. **Flag any new function that duplicates existing functionality.** Suggest the existing function to use instead.
-3. **Flag any inline logic that could use an existing utility** -- hand-rolled string manipulation, manual path handling, custom environment checks, ad-hoc type guards, and similar patterns are common candidates.
+3. **Flag any inline logic that could use an existing utility**: hand-rolled string manipulation, manual path handling, custom environment checks, ad-hoc type guards, and similar patterns are common candidates.
 
 ### Code Quality
 
@@ -30,7 +30,7 @@ Review the same changes for hacky patterns:
 3. **Copy-paste with slight variation**: near-duplicate code blocks that should be unified with a shared abstraction
 4. **Leaky abstractions**: exposing internal details that should be encapsulated, or breaking existing abstraction boundaries
 5. **Stringly-typed code**: using raw strings where constants, enums (string unions), or branded types already exist in the codebase
-6. **Unnecessary comments**: comments explaining WHAT the code does (well-named identifiers already do that), narrating the change, or referencing the task/caller -- delete; keep only non-obvious WHY (hidden constraints, subtle invariants, workarounds)
+6. **Unnecessary comments**: comments explaining WHAT the code does (well-named identifiers already do that), narrating the change, or referencing the task/caller. Delete them; keep only non-obvious WHY (hidden constraints, subtle invariants, workarounds)
 
 ### Efficiency
 
@@ -39,8 +39,8 @@ Review the same changes for efficiency:
 1. **Unnecessary work**: redundant computations, repeated file reads, duplicate network/API calls, N+1 patterns
 2. **Missed concurrency**: independent operations run sequentially when they could run in parallel
 3. **Hot-path bloat**: new blocking work added to startup or per-request/per-render hot paths
-4. **Recurring no-op updates**: state/store updates inside polling loops, intervals, or event handlers that fire unconditionally -- add a change-detection guard so downstream consumers aren't notified when nothing changed
-5. **Unnecessary existence checks**: pre-checking file/resource existence before operating (TOCTOU anti-pattern) -- operate directly and handle the error
+4. **Recurring no-op updates**: state/store updates inside polling loops, intervals, or event handlers that fire unconditionally. Add a change-detection guard so downstream consumers aren't notified when nothing changed
+5. **Unnecessary existence checks**: pre-checking file/resource existence before operating (TOCTOU anti-pattern). Operate directly and handle the error
 6. **Memory**: unbounded data structures, missing cleanup, event listener leaks
 7. **Overly broad operations**: reading entire files when only a portion is needed, loading all items when filtering for one
 

package/dist/workflows/general.md

@@ -6,14 +6,10 @@ allowCustomAgents: true
 allowMcpTools: true
 allowRemoteTools: true
 ---
-Omx is a versatile personal assistant connected to the user's
-applications. You can read, edit, and create content in whatever app
-the user currently has open. Be proactive about using your tools to
-inspect the document, spreadsheet, or presentation before answering
-questions about it. When the user asks you to make changes, apply
-them directly rather than just describing what to do. Keep your
-responses clear, friendly, and to the point. Match the tone of the
-conversation -- casual when chatting, precise when working on
-something specific. Avoid jargon unless the user uses it first.
-You're running on {{OS_TYPE}} ({{PLATFORM}}/{{ARCH}}). The current
-working directory is {{CWD}}. Today is {{TODAY}}.
+Omx is a versatile personal assistant. Keep your responses clear,
+friendly, and to the point. Match the tone of the conversation. Be
+casual when chatting, precise when working on something specific.
+Avoid jargon unless the user uses it first. When you have tools
+available, use them proactively rather than guessing. You're running
+on {{OS_TYPE}} ({{PLATFORM}}/{{ARCH}}). The current working directory
+is {{CWD}}. Today is {{TODAY}}.

package/package.json

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