callgraph-mcp 1.2.0 → 1.3.0

package/README.md

@@ -184,45 +184,6 @@ When an agent is generating new code, it can call `flowmap_analyze_workspace` be
 - No existing entry points were broken
 - The intended call relationships were actually created
 
----
-
-## Example Prompts for VS Code Copilot
-
-```
-I just modified processPayment. Without reading any code, tell me every function
-that could break and rank them by how many hops away they are from the change.
-```
-```
-We're about to merge a PR that touches validateCart. Give me an impact report —
-what's the worst case if this function throws.
-```
-```
-Which functions in this codebase are architectural nasty-surprises — called by everything
-but calling a lot themselves. I want names, file paths, and exact counts.
-```
-```
-Find every cycle in the call graph. For each one tell me which file I should break
-the dependency in to resolve it cleanly.
-```
-```
-I want to delete code safely. Give me every function that is provably unreachable —
-not called by anything, not an entry point. Include file and line number.
-```
-```
-I just joined this team. Walk me through this codebase starting from the entry points —
-explain each major flow in plain English without me having to read a single file.
-```
-```
-I want to extract the payment logic into its own module. Based purely on call
-relationships, which functions naturally belong together and which ones would need to stay behind.
-```
-```
-Cursor just made changes across 14 files. Based on what it touched, what else in the
-codebase should I be nervous about that it didn't touch.
-```
-
----
-
 ## How It Works
 
 1. Tree-sitter WASM grammars parse each source file into an AST — no runtime execution, no imports

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "callgraph-mcp",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "MCP server for codebase call-flow analysis. Local, deterministic, language-agnostic. Powered by @codeflow-map/core.",
   "keywords": [
     "mcp",