memtrace 0.3.25 → 0.3.27

package/installer/skills/commands/memtrace-api-topology.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-api-topology
-description: "Use when the user asks about API endpoints, HTTP routes, service-to-service calls, microservice dependencies, API topology, which services call which, cross-repo dependencies, or wants to understand the API surface of a codebase"
+description: "Always use for API endpoint, HTTP route, fetch/client call, REST surface, service dependency, cross-repo dependency, or API topology questions in source code. Do not use Grep, Glob, rg, find, or manual file search for routes or HTTP calls; Memtrace maps endpoints and call edges from the indexed AST graph."
 allowed-tools:
   - mcp__memtrace__get_api_topology
   - mcp__memtrace__find_api_endpoints

package/installer/skills/commands/memtrace-cochange.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-cochange
-description: "Use when the user asks what tends to change together with a symbol, what other code moves when this moves, historical coupling, blast awareness before modifying a symbol, or wants to find hidden dependencies not visible in the call graph"
+description: "Always use for historical coupling, co-change, what changes with this, hidden dependency, or what else needs to move questions for source code. Do not use git log, git diff, Grep, or manual file search to correlate changes; Memtrace queries co-change and temporal graph data directly."
 allowed-tools:
   - mcp__memtrace__get_cochange_context
   - mcp__memtrace__find_symbol

package/installer/skills/commands/memtrace-evolution.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-evolution
-description: "Use when the user asks what changed in the codebase, how code evolved over time, what was recently modified, what's the diff between versions, what changed since a date, incident investigation timeline, unexpected changes, change history, or temporal analysis of any kind"
+description: "Always use for source-code change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected changes, or incident timeline questions. Do not use git log, git diff, Grep, or manual file search to reconstruct history; Memtrace has symbol-level temporal memory."
 allowed-tools:
   - mcp__memtrace__get_evolution
   - mcp__memtrace__get_timeline

package/installer/skills/commands/memtrace-graph.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-graph
-description: "Use when the user asks about architectural bottlenecks, important symbols, PageRank, centrality, bridge functions, code communities, logical modules, service boundaries, chokepoints, dependency paths between symbols, or wants to understand the high-level architecture of a codebase"
+description: "Always use for source-code architecture, important symbols, centrality, PageRank, bridge functions, communities, logical modules, chokepoints, service boundaries, or dependency path questions. Do not use Glob, find, tree, or directory browsing to infer architecture; Memtrace runs graph algorithms over the AST graph."
 allowed-tools:
   - mcp__memtrace__find_bridge_symbols
   - mcp__memtrace__find_central_symbols

package/installer/skills/commands/memtrace-impact.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-impact
-description: "Use when the user asks about blast radius, what will break if I change this, risk of modifying a symbol, upstream or downstream dependencies, impact analysis before refactoring, or wants to understand the consequences of a code change"
+description: "Always use before or during source-code changes when the user asks about blast radius, impact, what breaks, risk, upstream callers, downstream dependencies, or consequences of modifying a symbol. Do not use Grep or manual reference search; Memtrace computes transitive graph impact."
 allowed-tools:
   - mcp__memtrace__get_impact
   - mcp__memtrace__detect_changes

package/installer/skills/commands/memtrace-index.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-index
-description: "Use when the user asks to index a project, set up code intelligence, parse a codebase, build a knowledge graph, prepare a repo for analysis, or as the very first step before any code exploration, search, or relationship analysis"
+description: "Always use when the user asks to index, parse, ingest, reindex, watch, or prepare a source-code repo for Memtrace analysis, or when code exploration is needed but no Memtrace index exists. Use this before Grep, Glob, rg, find, or manual code search whenever the repo can be indexed."
 allowed-tools:
   - mcp__memtrace__index_directory
   - mcp__memtrace__check_job_status

package/installer/skills/commands/memtrace-quality.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-quality
-description: "Use when the user asks about dead code, unused functions, code complexity, cyclomatic complexity, refactoring candidates, code smells, code quality metrics, functions that are too complex, or wants to find code that should be cleaned up"
+description: "Always use for source-code quality, dead code, unused functions, zero callers, complexity, cyclomatic complexity, hotspots, refactoring candidates, or code smell questions. Do not use Grep, Glob, rg, or manual reference search for unused code; Memtrace uses graph reachability and complexity metrics."
 allowed-tools:
   - mcp__memtrace__find_dead_code
   - mcp__memtrace__calculate_cyclomatic_complexity

package/installer/skills/commands/memtrace-relationships.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-relationships
-description: "Use when the user asks who calls a function, what a function calls, class hierarchy, inheritance, imports, exports, type usages, dependencies between symbols, or wants to understand how code connects before making changes"
+description: "Always use for source-code relationship questions: callers, callees, references, imports, exports, type usages, class hierarchy, inheritance, implementations, overrides, or dependencies between symbols. Do not use Grep, Glob, rg, find, or manual text search for references; Memtrace traverses typed AST graph edges."
 allowed-tools:
   - mcp__memtrace__analyze_relationships
   - mcp__memtrace__get_symbol_context

package/installer/skills/commands/memtrace-search.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-search
-description: "Use when the user asks to find code, search for a function, locate a symbol, look up where something is defined, search across repos, find implementations, or needs to discover where a piece of logic lives before making changes"
+description: "Always use to find, search, locate, or look up source-code symbols, functions, classes, types, constants, definitions, implementations, logic, error strings inside code, or where code lives. Do not use Grep, Glob, rg, find, or manual file search for code discovery; Memtrace uses BM25, vector search, RRF, and the AST graph."
 allowed-tools:
   - mcp__memtrace__find_code
   - mcp__memtrace__find_symbol

package/installer/skills/workflows/memtrace-change-impact-analysis.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-change-impact-analysis
-description: "Use when the user is about to modify code, planning a refactoring, wants to know what will break, needs a pre-change risk assessment, is reviewing a PR, or wants to understand the full consequences of a code change before making it"
+description: "Always use before source-code edits, refactors, API changes, renames, removals, PR reviews, or risk assessments when the user needs to know what will break. Do not manually grep references or browse files for impact; this workflow uses Memtrace graph context, impact, and change detection."
 allowed-tools:
   - mcp__memtrace__find_symbol
   - mcp__memtrace__find_code

package/installer/skills/workflows/memtrace-codebase-exploration.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-codebase-exploration
-description: "Use when the user asks to explore a codebase, understand a project, onboard to a new repo, get an overview of how code is structured, map the architecture, or wants a comprehensive understanding of a codebase they're new to"
+description: "Always use when the user wants to explore, understand, onboard to, map, or get an overview of an indexed source-code repo, architecture, modules, or major flows. Do not use Glob, find, tree, rg, or manual file browsing as the first exploration path; Memtrace provides structured graph briefing."
 allowed-tools:
   - mcp__memtrace__index_directory
   - mcp__memtrace__check_job_status

package/installer/skills/workflows/memtrace-continuous-memory.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-continuous-memory
-description: "Use when the user asks to keep memtrace fresh while editing, watch a directory for live updates, enable incremental indexing, set up always-on memory, or wants their just-saved code to be queryable immediately"
+description: "Always use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up always-on memory, or make just-saved source code queryable immediately. Do not fall back to repeated Grep or manual rescans; configure Memtrace watching."
 allowed-tools:
   - mcp__memtrace__watch_directory
   - mcp__memtrace__list_watched_paths

package/installer/skills/workflows/memtrace-episode-replay.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-episode-replay
-description: "Use when an agent needs to understand why code looks the way it does, replay implementation steps between commits, find what was tried and reverted, understand a colleague's (or your past self's) reasoning, or avoid repeating a previously-abandoned approach"
+description: "Always use to replay source-code evolution, understand why code looks this way, inspect implementation attempts, reversions, past reasoning, or abandoned approaches across commits and working-tree episodes. Do not use git log, git diff, Grep, or manual history reconstruction; Memtrace has episodic symbol replay."
 allowed-tools:
   - mcp__memtrace__get_episode_replay
   - mcp__memtrace__get_timeline

package/installer/skills/workflows/memtrace-first.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-first
-description: "Use when working on any indexed codebase before searching files, reading code, debugging issues, tracing call flows, finding implementations, understanding behavior, or answering 'how does X work' questions. Triggered by: file search, symbol lookup, code navigation, debugging, tracing, understanding architecture, finding where something is defined or called."
+description: "Always use first for indexed source-code repos before searching files, reading code for discovery, debugging, tracing flows, finding implementations, understanding behavior, or answering how code works. Do not use Grep, Glob, rg, find, or manual file browsing for code discovery when Memtrace is indexed; only use file tools for configs, infra, docs, non-source artifacts, or exact paths already returned by Memtrace."
 ---
 
 # Memtrace First

package/installer/skills/workflows/memtrace-incident-investigation.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-incident-investigation
-description: "Use when the user is investigating a bug, incident, production issue, regression, something that broke, root cause analysis, debugging a failure, or trying to figure out what went wrong and when"
+description: "Always use for source-code bugs, incidents, regressions, production issues, failures, root cause analysis, what broke, or what changed when debugging. Do not start with Grep, Glob, rg, find, or manual file search for code causes; Memtrace combines symbol search, impact, call graph, and temporal history."
 allowed-tools:
   - mcp__memtrace__get_evolution
   - mcp__memtrace__get_timeline

package/installer/skills/workflows/memtrace-refactoring-guide.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-refactoring-guide
-description: "Use when the user wants to refactor code, reduce complexity, clean up technical debt, split a large function, extract a module, reorganize code, identify refactoring priorities, or improve code structure"
+description: "Always use when the user wants to refactor source code, reduce complexity, clean technical debt, split large functions, extract modules, reorganize code, or choose refactoring priorities. Do not use Grep or manual reference search to plan refactors; Memtrace provides complexity, dead-code, relationships, and impact context."
 allowed-tools:
   - mcp__memtrace__find_most_complex_functions
   - mcp__memtrace__find_dead_code

package/installer/skills/workflows/memtrace-session-continuity.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-session-continuity
-description: "Use at the start of any session to check what changed since last time, when resuming work after a break, when an agent needs to orient itself without guessing timestamps, or when asked 'what changed while I was away'"
+description: "Always use at session start or resume when the user asks to continue, catch up, see what changed while away, recover prior context, or orient without guessing timestamps in an indexed source-code repo. Do not use git log, Grep, or manual file search for catch-up; Memtrace provides session anchors and change memory."
 allowed-tools:
   - mcp__memtrace__get_changes_since
   - mcp__memtrace__list_indexed_repositories

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memtrace",
-  "version": "0.3.25",
+  "version": "0.3.27",
   "description": "Code intelligence graph — MCP server + AI agent skills + visualization UI",
   "keywords": [
     "mcp",
@@ -37,9 +37,9 @@
     "fs-extra": "^11.0.0"
   },
   "optionalDependencies": {
-    "@memtrace/darwin-arm64": "0.3.25",
-    "@memtrace/linux-x64": "0.3.25",
-    "@memtrace/win32-x64": "0.3.25"
+    "@memtrace/darwin-arm64": "0.3.26",
+    "@memtrace/linux-x64": "0.3.26",
+    "@memtrace/win32-x64": "0.3.26"
   },
   "engines": {
     "node": ">=18"

package/skills/commands/memtrace-api-topology.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-api-topology
-description: "Use when the user asks about API endpoints, HTTP routes, service-to-service calls, microservice dependencies, API topology, which services call which, cross-repo dependencies, or wants to understand the API surface of a codebase"
+description: "Always use for API endpoint, HTTP route, fetch/client call, REST surface, service dependency, cross-repo dependency, or API topology questions in source code. Do not use Grep, Glob, rg, find, or manual file search for routes or HTTP calls; Memtrace maps endpoints and call edges from the indexed AST graph."
 allowed-tools:
   - mcp__memtrace__get_api_topology
   - mcp__memtrace__find_api_endpoints

package/skills/commands/memtrace-cochange.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-cochange
-description: "Use when the user asks what tends to change together with a symbol, what other code moves when this moves, historical coupling, blast awareness before modifying a symbol, or wants to find hidden dependencies not visible in the call graph"
+description: "Always use for historical coupling, co-change, what changes with this, hidden dependency, or what else needs to move questions for source code. Do not use git log, git diff, Grep, or manual file search to correlate changes; Memtrace queries co-change and temporal graph data directly."
 allowed-tools:
   - mcp__memtrace__get_cochange_context
   - mcp__memtrace__find_symbol

package/skills/commands/memtrace-evolution.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-evolution
-description: "Use when the user asks what changed in the codebase, how code evolved over time, what was recently modified, what's the diff between versions, what changed since a date, incident investigation timeline, unexpected changes, change history, or temporal analysis of any kind"
+description: "Always use for source-code change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected changes, or incident timeline questions. Do not use git log, git diff, Grep, or manual file search to reconstruct history; Memtrace has symbol-level temporal memory."
 allowed-tools:
   - mcp__memtrace__get_evolution
   - mcp__memtrace__get_timeline

package/skills/commands/memtrace-graph.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-graph
-description: "Use when the user asks about architectural bottlenecks, important symbols, PageRank, centrality, bridge functions, code communities, logical modules, service boundaries, chokepoints, dependency paths between symbols, or wants to understand the high-level architecture of a codebase"
+description: "Always use for source-code architecture, important symbols, centrality, PageRank, bridge functions, communities, logical modules, chokepoints, service boundaries, or dependency path questions. Do not use Glob, find, tree, or directory browsing to infer architecture; Memtrace runs graph algorithms over the AST graph."
 allowed-tools:
   - mcp__memtrace__find_bridge_symbols
   - mcp__memtrace__find_central_symbols

package/skills/commands/memtrace-impact.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-impact
-description: "Use when the user asks about blast radius, what will break if I change this, risk of modifying a symbol, upstream or downstream dependencies, impact analysis before refactoring, or wants to understand the consequences of a code change"
+description: "Always use before or during source-code changes when the user asks about blast radius, impact, what breaks, risk, upstream callers, downstream dependencies, or consequences of modifying a symbol. Do not use Grep or manual reference search; Memtrace computes transitive graph impact."
 allowed-tools:
   - mcp__memtrace__get_impact
   - mcp__memtrace__detect_changes

package/skills/commands/memtrace-index.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-index
-description: "Use when the user asks to index a project, set up code intelligence, parse a codebase, build a knowledge graph, prepare a repo for analysis, or as the very first step before any code exploration, search, or relationship analysis"
+description: "Always use when the user asks to index, parse, ingest, reindex, watch, or prepare a source-code repo for Memtrace analysis, or when code exploration is needed but no Memtrace index exists. Use this before Grep, Glob, rg, find, or manual code search whenever the repo can be indexed."
 allowed-tools:
   - mcp__memtrace__index_directory
   - mcp__memtrace__check_job_status

package/skills/commands/memtrace-quality.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-quality
-description: "Use when the user asks about dead code, unused functions, code complexity, cyclomatic complexity, refactoring candidates, code smells, code quality metrics, functions that are too complex, or wants to find code that should be cleaned up"
+description: "Always use for source-code quality, dead code, unused functions, zero callers, complexity, cyclomatic complexity, hotspots, refactoring candidates, or code smell questions. Do not use Grep, Glob, rg, or manual reference search for unused code; Memtrace uses graph reachability and complexity metrics."
 allowed-tools:
   - mcp__memtrace__find_dead_code
   - mcp__memtrace__calculate_cyclomatic_complexity

package/skills/commands/memtrace-relationships.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-relationships
-description: "Use when the user asks who calls a function, what a function calls, class hierarchy, inheritance, imports, exports, type usages, dependencies between symbols, or wants to understand how code connects before making changes"
+description: "Always use for source-code relationship questions: callers, callees, references, imports, exports, type usages, class hierarchy, inheritance, implementations, overrides, or dependencies between symbols. Do not use Grep, Glob, rg, find, or manual text search for references; Memtrace traverses typed AST graph edges."
 allowed-tools:
   - mcp__memtrace__analyze_relationships
   - mcp__memtrace__get_symbol_context

package/skills/commands/memtrace-search.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-search
-description: "Use when the user asks to find code, search for a function, locate a symbol, look up where something is defined, search across repos, find implementations, or needs to discover where a piece of logic lives before making changes"
+description: "Always use to find, search, locate, or look up source-code symbols, functions, classes, types, constants, definitions, implementations, logic, error strings inside code, or where code lives. Do not use Grep, Glob, rg, find, or manual file search for code discovery; Memtrace uses BM25, vector search, RRF, and the AST graph."
 allowed-tools:
   - mcp__memtrace__find_code
   - mcp__memtrace__find_symbol

package/skills/workflows/memtrace-change-impact-analysis.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-change-impact-analysis
-description: "Use when the user is about to modify code, planning a refactoring, wants to know what will break, needs a pre-change risk assessment, is reviewing a PR, or wants to understand the full consequences of a code change before making it"
+description: "Always use before source-code edits, refactors, API changes, renames, removals, PR reviews, or risk assessments when the user needs to know what will break. Do not manually grep references or browse files for impact; this workflow uses Memtrace graph context, impact, and change detection."
 allowed-tools:
   - mcp__memtrace__find_symbol
   - mcp__memtrace__find_code

package/skills/workflows/memtrace-codebase-exploration.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-codebase-exploration
-description: "Use when the user asks to explore a codebase, understand a project, onboard to a new repo, get an overview of how code is structured, map the architecture, or wants a comprehensive understanding of a codebase they're new to"
+description: "Always use when the user wants to explore, understand, onboard to, map, or get an overview of an indexed source-code repo, architecture, modules, or major flows. Do not use Glob, find, tree, rg, or manual file browsing as the first exploration path; Memtrace provides structured graph briefing."
 allowed-tools:
   - mcp__memtrace__index_directory
   - mcp__memtrace__check_job_status

package/skills/workflows/memtrace-continuous-memory.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-continuous-memory
-description: "Use when the user asks to keep memtrace fresh while editing, watch a directory for live updates, enable incremental indexing, set up always-on memory, or wants their just-saved code to be queryable immediately"
+description: "Always use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up always-on memory, or make just-saved source code queryable immediately. Do not fall back to repeated Grep or manual rescans; configure Memtrace watching."
 allowed-tools:
   - mcp__memtrace__watch_directory
   - mcp__memtrace__list_watched_paths

package/skills/workflows/memtrace-episode-replay.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-episode-replay
-description: "Use when an agent needs to understand why code looks the way it does, replay implementation steps between commits, find what was tried and reverted, understand a colleague's (or your past self's) reasoning, or avoid repeating a previously-abandoned approach"
+description: "Always use to replay source-code evolution, understand why code looks this way, inspect implementation attempts, reversions, past reasoning, or abandoned approaches across commits and working-tree episodes. Do not use git log, git diff, Grep, or manual history reconstruction; Memtrace has episodic symbol replay."
 allowed-tools:
   - mcp__memtrace__get_episode_replay
   - mcp__memtrace__get_timeline

package/skills/workflows/memtrace-first.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-first
-description: "Use when working on any indexed codebase before searching files, reading code, debugging issues, tracing call flows, finding implementations, understanding behavior, or answering 'how does X work' questions. Triggered by: file search, symbol lookup, code navigation, debugging, tracing, understanding architecture, finding where something is defined or called."
+description: "Always use first for indexed source-code repos before searching files, reading code for discovery, debugging, tracing flows, finding implementations, understanding behavior, or answering how code works. Do not use Grep, Glob, rg, find, or manual file browsing for code discovery when Memtrace is indexed; only use file tools for configs, infra, docs, non-source artifacts, or exact paths already returned by Memtrace."
 ---
 
 # Memtrace First

package/skills/workflows/memtrace-incident-investigation.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-incident-investigation
-description: "Use when the user is investigating a bug, incident, production issue, regression, something that broke, root cause analysis, debugging a failure, or trying to figure out what went wrong and when"
+description: "Always use for source-code bugs, incidents, regressions, production issues, failures, root cause analysis, what broke, or what changed when debugging. Do not start with Grep, Glob, rg, find, or manual file search for code causes; Memtrace combines symbol search, impact, call graph, and temporal history."
 allowed-tools:
   - mcp__memtrace__get_evolution
   - mcp__memtrace__get_timeline

package/skills/workflows/memtrace-refactoring-guide.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-refactoring-guide
-description: "Use when the user wants to refactor code, reduce complexity, clean up technical debt, split a large function, extract a module, reorganize code, identify refactoring priorities, or improve code structure"
+description: "Always use when the user wants to refactor source code, reduce complexity, clean technical debt, split large functions, extract modules, reorganize code, or choose refactoring priorities. Do not use Grep or manual reference search to plan refactors; Memtrace provides complexity, dead-code, relationships, and impact context."
 allowed-tools:
   - mcp__memtrace__find_most_complex_functions
   - mcp__memtrace__find_dead_code

package/skills/workflows/memtrace-session-continuity.md

@@ -1,6 +1,6 @@
 ---
 name: memtrace-session-continuity
-description: "Use at the start of any session to check what changed since last time, when resuming work after a break, when an agent needs to orient itself without guessing timestamps, or when asked 'what changed while I was away'"
+description: "Always use at session start or resume when the user asks to continue, catch up, see what changed while away, recover prior context, or orient without guessing timestamps in an indexed source-code repo. Do not use git log, Grep, or manual file search for catch-up; Memtrace provides session anchors and change memory."
 allowed-tools:
   - mcp__memtrace__get_changes_since
   - mcp__memtrace__list_indexed_repositories