Skip to main content
skill CX Codex

vesalius-code-map — Claude Code skill for code maps

vesalius-code-map is a Claude Code skill that queries Vesalius tools about a repository. It joins questions about call sites, feature locations, file contents, architecture, and import cycles.

MIT ★ 81 updated 2026-11-06

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add haplollc/Vesalius
/plugin install vesalius@haplo
Open on GitHub

What vesalius-code-map does

vesalius-code-map queries Vesalius’s code graph through MCP instead of searching source text. usages finds callers and references, feature_map groups relevant types and functions by role, and outline lists declarations and calls in a file. The tools are read-only.

architecture maps project targets and dependency direction; dependency_cycles reports import cycles with their source lines. The full MCP profile also exposes repo_report for diagnostics, hotspots, and a repository overview. A Vesalius server must serve the repository Claude Code is working in. Select one with vesalius mcp --repo /path/to/repo or set VESALIUS_REPO.

What it helps with

  • trace which functions call a symbol
  • locate the code that handles a feature
  • inspect declarations and calls in a file
  • map dependency direction across a project
  • find circular imports and their source lines

Example prompts for the agent

  • Show which functions call createUser and where they are defined.
  • Find the files that handle purchases and explain how data is saved.
  • Check this project for circular imports and show the dependency lines.

How to install vesalius-code-map

1Plugin marketplace

/plugin marketplace add haplollc/Vesalius
/plugin install vesalius@haplo

This installs the whole vesalius plugin with all its skills

2Skills CLI (Vercel)

npx skills add haplollc/Vesalius --skill vesalius-code-map -a claude-code

3Manually: put the files in place

~/.claude/skills/vesalius-code-map/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vesalius-code-map/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vesalius-code-map

How do I install vesalius-code-map in Claude Code?

Add the marketplace with /plugin marketplace add haplollc/Vesalius, then install the skill with /plugin install vesalius@haplo.

What does vesalius-code-map do?

It queries Vesalius MCP tools to inspect references, file structure, project architecture, and dependency cycles. Its tools do not modify files.

What does vesalius-code-map need to run?

A Vesalius MCP server must serve the repository Claude Code is using. Choose the repository with vesalius mcp --repo /path/to/repo or set VESALIUS_REPO.

Source text

SKILL.md · MIT
---
name: vesalius-code-map
description: Ask Vesalius about a codebase through its MCP tools instead of grepping: usages, feature_map, outline, architecture, and dependency_cycles. Use when answering questions about who calls or uses something, where a feature lives, what a file contains, how a project is put together, or whether circular imports exist.
---

# Vesalius code map

Vesalius is a precomputed, on-device code graph of the repository. Its
tools return file and line evidence, usually in one call. Every tool is
read-only. Use Grep for literal text or regex instead.

## Tools

| Tool | Ask it | What comes back |
| --- | --- | --- |
| `usages` | Who calls X? What uses this file? What breaks if I rename X? | Uses as file and line plus code, grouped by the function they sit in, plus a completeness check. With a change of rename, signature, or remove: the edit list and the tests to run. |
| `feature_map` | Where are purchases handled? How is data persisted? | The core types and functions grouped by role, with decisive lines, framework and input/output calls, config links, and call sites. |
| `outline` | What is in this file, type, or function? | Declarations with signatures and line ranges, first doc sentences, and calls in order. Cheaper than reading the file. |
| `architecture` | How is this project put together? | Targets and their product types, packages, folders, dependency direction, cycles, and cross-target links. |
| `dependency_cycles` | Do we have circular imports? | Every cycle in scope with each edge's import line and where the imported names are used, plus what was scanned. |

Under the `full` MCP profile there is a sixth tool, `repo_report`, for
health score, diagnostics, hotspots, unused code, overview, and finding
files by name.

## Notes

- If a `usages` result says complete, do not re-grep it. If it lists
  unresolved sites, check only those.
- The server serves the repository Claude Code is working in. Pin one
  repository with `vesalius mcp --repo /path/to/repo` in a manual
  registration, or set `VESALIUS_REPO`.
- `vesalius doctor` checks the connection any time. `vesalius stats`
  shows what Claude asked.

© Haplo · MIT · haplollc/Vesalius

Similar skills

All skills for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open