V-NOC 推出支援 VS Code 與 Cursor 的擴充功能,探索呼叫樹並連結文件與程式碼
I built a VS Code extension to explore call trees and keep docs linked to code
作者開發了 V-NOC,一款支援 VS Code 和 Cursor 的圖形化擴充功能,可探索函式呼叫樹並把 Markdown 文件連結至程式碼節點。用戶可查看函式的呼叫者、被呼叫者及相關程式碼片段;文件可附於函式、類別、檔案或資料夾,並存放在專案儲存庫中,透過 Git 追蹤、檢視和分享。作者正開發 CLI,讓編碼智能體讀寫附於程式碼節點的 Markdown。
When I’m working on one problem, the code I need is often spread across several files. I keep jumping between them, following calls and holding the connections in my head.
I’m building V-NOC to make that easier. It’s a graph-based extension for VS Code and Cursor that lets you focus on one part of a codebase and bring its context together.
Focus on one function
You can select a function, navigate its callers and callees, and see the relevant code slice.
For example, when investigating a checkout failure, you might want to follow the path from checkout to inventory to payment. The goal is to explore that small system without the rest of the project getting in the way.
Keep documentation linked to code
You can attach Markdown documentation to a function, class, file, or folder.
The docs stay linked to those nodes and live in your repository. You can track changes, review them, and share them with teammates through Git.
A function can have its detailed explanation, while a class or folder can describe how the larger pieces fit together.
From a standalone tool to an extension
I recently rewrote the Python static analyzer in Rust and replaced the graph database with file-tree storage organized like Git.
Those changes made it small and fast enough to bring into an editor extension, so you can use it where you already work.
What I’m adding next
I’m working on a CLI so coding agents can read and write Markdown attached to code nodes.
That could include documentation, implementation plans, and walkthroughs of how a feature works. The aim is to keep those explanations connected to the code they describe.
Looking for early testers
This is an early release, and I’d like feedback from people trying it on their own projects.
If you try it on your Python project, I’d love to hear whether the call tree helps you follow the code, whether attaching docs feels useful, and anything that breaks or feels confusing.
How do you currently keep track of the code and context needed to work on one problem?
來源:DEV Community · dev.to

