@nano-step/skill-manager 5.5.3 → 5.6.0

package/dist/index.js

@@ -123,6 +123,7 @@ async function run() {
         .command("install [name]")
         .description("Install a skill from the catalog")
         .option("--all", "Install all available skills")
+        .option("--force", "Force reinstall even if same version is installed")
         .action(async (name, options) => {
         const paths = await (0, utils_1.detectOpenCodePaths)();
         await (0, state_1.migrateV4State)(paths.configDir, paths.stateFilePath, paths.skillsDir);
@@ -135,11 +136,11 @@ async function run() {
                 return;
             }
             for (const entry of catalog) {
-                await (0, installer_1.installSkill)(entry.manifest.name, paths);
+                await (0, installer_1.installSkill)(entry.manifest.name, paths, options.force);
             }
         }
         else if (name) {
-            await (0, installer_1.installSkill)(name, paths);
+            await (0, installer_1.installSkill)(name, paths, options.force);
         }
         else {
             console.error(chalk_1.default.red("Please specify a skill name or use --all."));
@@ -158,11 +159,12 @@ async function run() {
     program
         .command("update [name]")
         .description("Update installed skill(s) to latest catalog version")
-        .action(async (name) => {
+        .option("--force", "Force update even if same version is installed")
+        .action(async (name, options) => {
         const paths = await (0, utils_1.detectOpenCodePaths)();
         await (0, state_1.migrateV4State)(paths.configDir, paths.stateFilePath, paths.skillsDir);
         if (name) {
-            await (0, installer_1.updateSkill)(name, paths);
+            await (0, installer_1.updateSkill)(name, paths, options.force);
         }
         else {
             const state = await (0, state_1.loadState)(paths.stateFilePath);
@@ -172,7 +174,7 @@ async function run() {
                 return;
             }
             for (const skillName of installed) {
-                await (0, installer_1.updateSkill)(skillName, paths);
+                await (0, installer_1.updateSkill)(skillName, paths, options.force);
             }
         }
     });

package/dist/installer.d.ts

@@ -1,4 +1,4 @@
 import { OpenCodePaths } from "./utils";
-export declare function installSkill(name: string, paths: OpenCodePaths): Promise<void>;
+export declare function installSkill(name: string, paths: OpenCodePaths, force?: boolean): Promise<void>;
 export declare function removeSkill(name: string, paths: OpenCodePaths): Promise<void>;
-export declare function updateSkill(name: string, paths: OpenCodePaths): Promise<void>;
+export declare function updateSkill(name: string, paths: OpenCodePaths, force?: boolean): Promise<void>;

package/dist/installer.js

@@ -14,11 +14,11 @@ const registry_1 = require("./registry");
 const state_1 = require("./state");
 const config_1 = require("./config");
 const remote_registry_1 = require("./remote-registry");
-async function installFromDir(manifest, sourceDir, paths, source) {
+async function installFromDir(manifest, sourceDir, paths, source, force) {
     const state = await (0, state_1.loadState)(paths.stateFilePath);
     const existing = state.skills[manifest.name];
-    if (existing && existing.version === manifest.version) {
-        console.log(chalk_1.default.yellow(`Skill "${manifest.name}" is already installed at v${manifest.version}.`));
+    if (existing && existing.version === manifest.version && !force) {
+        console.log(chalk_1.default.yellow(`Skill "${manifest.name}" is already installed at v${manifest.version}. Use --force to reinstall.`));
         return;
     }
     await (0, utils_1.ensureDirExists)(paths.skillsDir);
@@ -34,13 +34,14 @@ async function installFromDir(manifest, sourceDir, paths, source) {
     };
     await (0, state_1.saveState)(paths.stateFilePath, state);
     const sourceLabel = source === "private" ? chalk_1.default.magenta(" (private)") : "";
-    console.log(chalk_1.default.green(`✓ Installed ${manifest.name} v${manifest.version}${sourceLabel}`));
+    const forceLabel = force && existing ? " (forced)" : "";
+    console.log(chalk_1.default.green(`✓ Installed ${manifest.name} v${manifest.version}${sourceLabel}${forceLabel}`));
 }
-async function installSkill(name, paths) {
+async function installSkill(name, paths, force) {
     const localManifest = await (0, registry_1.getSkillManifest)(paths.packageSkillsDir, name);
     if (localManifest) {
         const packageSkillDir = path_1.default.join(paths.packageSkillsDir, name);
-        await installFromDir(localManifest, packageSkillDir, paths, "public");
+        await installFromDir(localManifest, packageSkillDir, paths, "public", force);
         return;
     }
     const remoteManifest = await (0, remote_registry_1.getRemoteSkillManifest)(name);
@@ -48,7 +49,7 @@ async function installSkill(name, paths) {
         const tempDir = await (0, remote_registry_1.downloadSkillToTemp)(name);
         if (tempDir) {
             try {
-                await installFromDir(remoteManifest, tempDir, paths, "private");
+                await installFromDir(remoteManifest, tempDir, paths, "private", force);
             }
             finally {
                 await fs_extra_1.default.remove(tempDir);
@@ -95,7 +96,7 @@ async function removeSkill(name, paths) {
     await (0, state_1.saveState)(paths.stateFilePath, state);
     console.log(chalk_1.default.green(`✓ Removed ${name}`));
 }
-async function updateSkill(name, paths) {
+async function updateSkill(name, paths, force) {
     const state = await (0, state_1.loadState)(paths.stateFilePath);
     if (!state.skills[name]) {
         console.error(chalk_1.default.red(`Skill "${name}" is not installed. Use 'skill-manager install ${name}' first.`));
@@ -104,8 +105,8 @@ async function updateSkill(name, paths) {
     const installed = state.skills[name];
     const localManifest = await (0, registry_1.getSkillManifest)(paths.packageSkillsDir, name);
     if (localManifest) {
-        if (installed.version === localManifest.version) {
-            console.log(chalk_1.default.yellow(`Skill "${name}" is already at v${localManifest.version} (up to date).`));
+        if (installed.version === localManifest.version && !force) {
+            console.log(chalk_1.default.yellow(`Skill "${name}" is already at v${localManifest.version} (up to date). Use --force to override.`));
             return;
         }
         const packageSkillDir = path_1.default.join(paths.packageSkillsDir, name);
@@ -120,13 +121,14 @@ async function updateSkill(name, paths) {
             location: installed.location,
         };
         await (0, state_1.saveState)(paths.stateFilePath, state);
-        console.log(chalk_1.default.green(`✓ Updated ${name} from v${installed.version} to v${localManifest.version}`));
+        const forceLabel = force && installed.version === localManifest.version ? " (forced)" : "";
+        console.log(chalk_1.default.green(`✓ Updated ${name} from v${installed.version} to v${localManifest.version}${forceLabel}`));
         return;
     }
     const remoteManifest = await (0, remote_registry_1.getRemoteSkillManifest)(name);
     if (remoteManifest) {
-        if (installed.version === remoteManifest.version) {
-            console.log(chalk_1.default.yellow(`Skill "${name}" is already at v${remoteManifest.version} (up to date).`));
+        if (installed.version === remoteManifest.version && !force) {
+            console.log(chalk_1.default.yellow(`Skill "${name}" is already at v${remoteManifest.version} (up to date). Use --force to override.`));
             return;
         }
         const tempDir = await (0, remote_registry_1.downloadSkillToTemp)(name);
@@ -143,7 +145,8 @@ async function updateSkill(name, paths) {
                     location: installed.location,
                 };
                 await (0, state_1.saveState)(paths.stateFilePath, state);
-                console.log(chalk_1.default.green(`✓ Updated ${name} from v${installed.version} to v${remoteManifest.version} (private)`));
+                const remoteForceLabel = force && installed.version === remoteManifest.version ? " (forced)" : "";
+                console.log(chalk_1.default.green(`✓ Updated ${name} from v${installed.version} to v${remoteManifest.version} (private)${remoteForceLabel}`));
             }
             finally {
                 await fs_extra_1.default.remove(tempDir);

package/dist/utils.d.ts

@@ -1,4 +1,4 @@
-export declare const MANAGER_VERSION = "5.5.3";
+export declare const MANAGER_VERSION = "5.6.0";
 export interface SkillManifest {
     name: string;
     version: string;

package/dist/utils.js

@@ -13,7 +13,7 @@ exports.writeText = writeText;
 const path_1 = __importDefault(require("path"));
 const os_1 = __importDefault(require("os"));
 const fs_extra_1 = __importDefault(require("fs-extra"));
-exports.MANAGER_VERSION = "5.5.3";
+exports.MANAGER_VERSION = "5.6.0";
 async function detectOpenCodePaths() {
     const homeConfig = path_1.default.join(os_1.default.homedir(), ".config", "opencode");
     const cwd = process.cwd();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nano-step/skill-manager",
-  "version": "5.5.3",
+  "version": "5.6.0",
   "description": "CLI tool that installs and manages AI agent skills, MCP tool routing, and workflow configurations.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/private-catalog.json

@@ -16,8 +16,8 @@
   },
   {
     "name": "pr-code-reviewer",
-    "version": "2.6.0",
-    "description": "Comprehensive code review with 4 parallel subagents and GitHub Copilot-style PR summaries"
+    "version": "7.1.0",
+    "description": "PR review with MANDATORY cross-repo consumer search, nano-brain code intelligence, and better-context structural analysis. READ-ONLY — no comments, pushes, or code fixes."
   },
   {
     "name": "rri-t-testing",

package/skills/nano-brain/AGENTS_SNIPPET.md

@@ -37,10 +37,25 @@ memory_write("## Summary\n- Decision: ...\n- Why: ...\n- Files: ...")
 # File: ~/.nano-brain/memory/YYYY-MM-DD-summary.md
 ```
 
-### When to Search Memory vs Codebase
+### Code Intelligence Tools
+
+nano-brain also provides symbol-level code analysis (requires `memory_index_codebase` first):
+
+| I want to... | MCP Tool |
+|--------------|----------|
+| Understand a symbol's callers/callees/flows | `code_context(name="functionName")` |
+| Assess risk of changing a symbol | `code_impact(target="className", direction="upstream")` |
+| Map my git changes to affected symbols | `code_detect_changes(scope="all")` |
+
+Use `file_path` parameter to disambiguate when multiple symbols share the same name.
+
+### When to Search Memory vs Codebase vs Code Intelligence
 
 - **"Have we done this before?"** → `memory_query` or `npx nano-brain query` (searches past sessions)
 - **"Where is this in the code?"** → grep / ast-grep (searches current files)
 - **"How does this concept work here?"** → Both (memory for past context + grep for current code)
+- **"What calls this function?"** → `code_context` (symbol graph relationships)
+- **"What breaks if I change X?"** → `code_impact` (dependency + flow analysis)
+- **"What did my changes affect?"** → `code_detect_changes` (git diff to symbol mapping)
 
 <!-- OPENCODE-MEMORY:END -->

package/skills/nano-brain/SKILL.md

@@ -1,14 +1,23 @@
+---
+name: nano-brain
+description: Provide persistent memory and code intelligence for AI coding agents; use for hybrid search, cross-session recall, symbol analysis, and impact checks.
+compatibility: OpenCode
+metadata:
+  author: nano-step
+  version: 2.1.0
+---
+
 # nano-brain
 
-Persistent memory for AI coding agents. Hybrid search (BM25 + semantic + LLM reranking) across past sessions, codebase, notes, and daily logs.
+Provide persistent memory for AI coding agents. Run hybrid search (BM25 + semantic + LLM reranking) across past sessions, codebase, notes, and daily logs.
 
 ## Slash Commands
 
 | Command | When |
 |---------|------|
-| `/nano-brain-init` | First-time workspace setup |
-| `/nano-brain-status` | Health check, embedding progress |
-| `/nano-brain-reindex` | After branch switch, pull, or major changes |
+| `/nano-brain-init` | Run first-time workspace setup |
+| `/nano-brain-status` | Check health, embedding progress |
+| `/nano-brain-reindex` | Run after branch switch, pull, or major changes |
 
 ## When to Use Memory
 
@@ -17,25 +26,44 @@ Persistent memory for AI coding agents. Hybrid search (BM25 + semantic + LLM rer
 
 ## Access Methods: MCP vs CLI
 
-nano-brain can be accessed via **MCP tools** (when the MCP server is configured) or **CLI** (always available).
+Access nano-brain via **MCP tools** (when the MCP server is configured) or **CLI** (always available).
 
 **Detection:** Try calling `memory_status` MCP tool first. If it fails with "MCP server not found", fall back to CLI.
 
 ### MCP Tools (preferred when available)
 
-| Need | MCP Tool |
-|------|----------|
-| Exact keyword (error msg, function name) | `memory_search` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_search")` |
-| Conceptual ("how does auth work") | `memory_vsearch` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_vsearch")` |
-| Best quality, complex question | `memory_query` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_query")` |
-| Retrieve specific doc | `memory_get` / `memory_multi_get` |
-| Save insight or decision (append to daily log) | `memory_write` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_write")` |
-| Set/update a keyed memory (overwrites previous) | `memory_set` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_set")` |
-| Delete a keyed memory | `memory_delete` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_delete")` |
-| List all keyed memories | `memory_keys` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_keys")` |
-| Check health | `memory_status` via `skill_mcp(mcp_name="nano-brain", tool_name="memory_status")` |
-| Rescan source files | `memory_index_codebase` |
-| Refresh all indexes | `memory_update` |
+- **`memory_search`** — recall a specific error string or function name from past sessions.
+  Example: `skill_mcp(mcp_name="nano-brain", tool_name="memory_search", arguments={ query: "ECONNREFUSED redis timeout" })`
+- **`memory_vsearch`** — explore a fuzzy concept when you do not know the exact wording.
+  Example: `memory_vsearch("caching strategy for user sessions")`
+- **`memory_query`** — get the best hybrid answer for a complex, multi-part question.
+  Example: `memory_query("how did we handle rate limiting in the payment service")`
+- **`memory_get`** — pull one known doc by ID or path.
+  Example: `memory_get(id="#a1b2c3")`
+- **`memory_multi_get`** — fetch a set of known docs by pattern.
+  Example: `memory_multi_get(pattern="decisions/2025-*/auth-*.md")`
+- **`memory_write`** — log a decision or insight for future recall.
+  Example: `memory_write("## Decision: Use Redis Streams over Bull queues\n- Why: retries need ordered replay")`
+- **`memory_set`** — store a keyed note you plan to update over time.
+  Example: `memory_set(key="payments-rate-limit", content="429s come from gateway, not nginx")`
+- **`memory_delete`** — remove a stale keyed note that is no longer accurate.
+  Example: `memory_delete(key="legacy-redis-metrics")`
+- **`memory_keys`** — list all keyed notes to see what is tracked.
+  Example: `memory_keys()`
+- **`memory_status`** — verify MCP health or embedding progress before searching.
+  Example: `memory_status()`
+- **`memory_index_codebase`** — index source files before using code intelligence tools.
+  Example: `memory_index_codebase(root="/Users/tamlh/workspaces/self/AI/Tools")`
+- **`memory_update`** — refresh all indexes after big changes or repo syncs.
+  Example: `memory_update()`
+- **`memory_focus`** — inspect dependencies for a specific file you are editing.
+  Example: `memory_focus(filePath="/src/api/routes/auth.ts")`
+- **`memory_graph_stats`** — check dependency graph size and coverage.
+  Example: `memory_graph_stats()`
+- **`memory_symbols`** — find where cross-repo infrastructure symbols are defined or used.
+  Example: `memory_symbols(type="redis_key", pattern="session:*")`
+- **`memory_impact`** — see which repos or services are affected by a symbol.
+  Example: `memory_impact(type="mysql_table", pattern="orders")`
 
 ### CLI Fallback (always available)
 
@@ -69,9 +97,23 @@ Works with both MCP and CLI (`-c` flag):
 - `memory` — curated notes only
 - Omit — search everything (recommended)
 
+## Code Intelligence Tools (MCP)
+
+Use symbol-level analysis powered by Tree-sitter AST parsing. Require codebase indexing.
+
+- **`code_context`** — trace callers, callees, and flows around a symbol.
+  Example: `code_context(name="processPayment")`
+- **`code_impact`** — evaluate upstream or downstream risk before refactors.
+  Example: `code_impact(target="DatabaseClient", direction="upstream")`
+- **`code_detect_changes`** — map current git diffs to symbols and flows.
+  Example: `code_detect_changes(scope="all")`
+
+**Details and examples:** `references/code-intelligence.md`
+
 ## Memory vs Native Tools
 
 Memory excels at **recall and semantics** — past sessions, conceptual search, cross-project knowledge.
 Native tools (grep, ast-grep, glob) excel at **precise code patterns** — exact matches, AST structure.
+Code intelligence tools excel at **structural relationships** — call graphs, impact analysis, flow detection.
 
-**They are complementary.** Use both.
+**They are complementary.** Use all three.

package/skills/nano-brain/references/code-intelligence.md

@@ -0,0 +1,57 @@
+---
+name: nano-brain code intelligence
+description: Use MCP code_context, code_impact, and code_detect_changes for symbol-level analysis, impact checks, and diff mapping.
+---
+
+# Code Intelligence (nano-brain)
+
+## Overview
+
+Run code intelligence when symbol relationships, impact analysis, or diff-to-symbol mapping is needed. Ensure indexing is done with `memory_index_codebase` before using these tools.
+
+## code_context — 360-degree symbol view
+
+Return callers, callees, cluster membership, execution flows, and infrastructure connections for any function/class/method.
+
+```
+skill_mcp(mcp_name="nano-brain", tool_name="code_context", arguments={"name": "handleRequest"})
+skill_mcp(mcp_name="nano-brain", tool_name="code_context", arguments={"name": "helper", "file_path": "/src/utils.ts"})
+```
+
+Use `file_path` to disambiguate when multiple symbols share the same name.
+
+## code_impact — dependency analysis
+
+Traverse the symbol graph to find affected symbols and flows. Return a risk level (LOW/MEDIUM/HIGH/CRITICAL).
+
+```
+skill_mcp(mcp_name="nano-brain", tool_name="code_impact", arguments={"target": "DatabaseClient", "direction": "upstream"})
+skill_mcp(mcp_name="nano-brain", tool_name="code_impact", arguments={"target": "processOrder", "direction": "downstream", "max_depth": 3})
+```
+
+- `upstream` = "who calls this?" (callers, consumers)
+- `downstream` = "what does this call?" (callees, dependencies)
+
+## code_detect_changes — git diff to symbol mapping
+
+Map current git changes to affected symbols and execution flows.
+
+```
+skill_mcp(mcp_name="nano-brain", tool_name="code_detect_changes", arguments={"scope": "staged"})
+skill_mcp(mcp_name="nano-brain", tool_name="code_detect_changes", arguments={"scope": "all"})
+```
+
+Scopes: `unstaged`, `staged`, `all` (default).
+
+## When to Use Code Intelligence vs Memory vs Native Tools
+
+| Question | Tool |
+|----------|------|
+| "What calls function X?" | `code_context` |
+| "What breaks if I change X?" | `code_impact` |
+| "What did I change and what's affected?" | `code_detect_changes` |
+| "Have we done this before?" | `memory_query` |
+| "Find exact string in code" | grep / ast-grep |
+| "How does auth work conceptually?" | `memory_vsearch` |
+
+Code intelligence requires indexing. Run `memory_index_codebase` first if the workspace has not been indexed.

package/skills/nano-brain/skill.json

@@ -1,7 +1,7 @@
 {
     "name": "nano-brain",
-    "version": "1.0.0",
-    "description": "Persistent memory for AI coding agents. Hybrid search (BM25 + semantic + LLM reranking) across past sessions, codebase, notes, and daily logs.",
+    "version": "2.1.0",
+    "description": "Persistent memory and code intelligence for AI coding agents. Hybrid search, cross-session recall, symbol analysis, and impact checks.",
     "compatibility": "OpenCode",
     "agent": null,
     "commands": [],
@@ -10,6 +10,9 @@
         "persistence",
         "search",
         "context",
-        "sessions"
+        "sessions",
+        "code-intelligence",
+        "symbol-analysis",
+        "impact-analysis"
     ]
 }

package/skills/skill-management/references/tool-categories.md

@@ -145,6 +145,58 @@ Notes:
 - Tools require a page context; select or create a page first.
 - Prefer take_snapshot for element discovery before click/hover/drag.
 
+## Memory & Knowledge Category (Example)
+
+Category name: Memory & Knowledge
+Keywords: memory, search, recall, context, session, codebase, knowledge, symbol, impact, dependency, graph, focus
+Description: Persistent memory, hybrid search, code intelligence, and cross-repo symbol analysis via nano-brain.
+
+Example tools that might appear in this category:
+- memory_search
+  - BM25 full-text keyword search across indexed documents.
+- memory_vsearch
+  - Semantic vector search using embeddings.
+- memory_query
+  - Full hybrid search with query expansion, RRF fusion, and LLM reranking.
+- memory_get
+  - Retrieve a document by path or docid.
+- memory_multi_get
+  - Batch retrieve documents by glob pattern or comma-separated list.
+- memory_write
+  - Write content to daily log with workspace context.
+- memory_set
+  - Set/update a keyed memory (overwrites previous value).
+- memory_delete
+  - Delete a keyed memory.
+- memory_keys
+  - List all keyed memories.
+- memory_status
+  - Show index health, collection info, and model status.
+- memory_index_codebase
+  - Index codebase files in the current workspace.
+- memory_update
+  - Trigger immediate reindex of all collections.
+- memory_focus
+  - Get dependency graph context for a specific file.
+- memory_graph_stats
+  - Get statistics about the file dependency graph.
+- memory_symbols
+  - Query cross-repo symbols (Redis keys, PubSub channels, MySQL tables, API endpoints, HTTP calls, Bull queues).
+- memory_impact
+  - Analyze cross-repo impact of a symbol (writers vs readers, publishers vs subscribers).
+- code_context
+  - 360-degree view of a code symbol — callers, callees, cluster, flows, infrastructure connections.
+- code_impact
+  - Analyze impact of changing a symbol — upstream/downstream dependencies, affected flows, risk level.
+- code_detect_changes
+  - Detect changed symbols and affected flows from git diff.
+
+Notes:
+- Memory tools require nano-brain MCP server to be configured.
+- Code intelligence tools require prior indexing via memory_index_codebase.
+- Use memory_query for best quality results (combines BM25 + vector + reranking).
+- Use memory_search for exact keyword matches, memory_vsearch for conceptual search.
+
 ## GitHub Operations Category (Example)
 
 Category name: GitHub Operations
@@ -220,13 +272,18 @@ Example tools that might appear in this category:
 ## Category Boundary Examples
 Use these to avoid misclassification:
 - "take a screenshot" -> Browser Automation
+- "recall past decisions" -> Memory & Knowledge
 - "list pull requests" -> GitHub Operations
 - "list graphql queries" -> GraphQL Introspection
 - "find docs for lodash" -> Documentation Lookup
+- "what calls this function" -> Memory & Knowledge
+- "search past sessions" -> Memory & Knowledge
 
 ## Common Intent Phrases by Category
 Browser intents:
 - "click", "hover", "fill form", "upload file", "take snapshot"
+Memory intents:
+- "recall", "remember", "past session", "what did we do", "search memory", "save decision", "code context", "impact analysis", "what calls", "dependency graph"
 GitHub intents:
 - "get PR", "list issues", "search repo", "read file"
 GraphQL intents:
@@ -242,6 +299,7 @@ Docs intents:
 
 ## Category Ownership Notes (Semantic Only)
 - Browser Automation: runtime web UI interaction and diagnostics.
+- Memory & Knowledge: persistent cross-session memory, hybrid search, code intelligence, and cross-repo symbol analysis.
 - GitHub Operations: repository metadata and collaboration artifacts.
 - GraphQL Introspection: schema discovery and field metadata only.
 - Documentation Lookup: documentation discovery and lookup.