Knowledge graph integration for token-efficient codebase understanding. Uses codebase-memory MCP for AST indexing, dependency graphs, and smart context selection. 6-71x token savings vs raw file reading.
npx skills add https://github.com/vibeeval/vibecosystem --skill knowledge-graph
Transform any codebase into a queryable knowledge graph using codebase-memory MCP server. Instead of reading entire files, query the graph for exactly the context you need.
Token savings: 6-71x reduction compared to raw file reading.
~/bin/codebase-memory-mcp or via npm)~/.mcp.json:{
"mcpServers": {
"codebase-memory": {
"command": "/path/to/codebase-memory-mcp",
"args": []
}
}
}
mcp__codebase-memory__index_repository
project_name: "my-project"
repo_path: "/path/to/repo"
First index takes 30-120s depending on repo size. Subsequent updates are incremental.
mcp__codebase-memory__index_status
project_name: "my-project"
mcp__codebase-memory__search_code
project_name: "my-project"
query: "authentication middleware"
Returns relevant code snippets without reading entire files.
mcp__codebase-memory__get_architecture
project_name: "my-project"
Returns high-level architecture: modules, dependencies, entry points.
mcp__codebase-memory__trace_call_path
project_name: "my-project"
from_symbol: "handleLogin"
to_symbol: "validateToken"
mcp__codebase-memory__query_graph
project_name: "my-project"
query: "what depends on auth module?"
| Scenario | Without Graph | With Graph |
|----------|--------------|------------|
| Code review | Read all changed files + imports | Query impact of changes |
| Bug investigation | Read 10-20 files manually | Trace call path to bug |
| Refactoring | Read entire module | Query all dependents |
| Architecture review | Read project top-down | Get architecture overview |
Before reviewing, query the graph for the blast radius of changes:
search_code("functions that call {changed_function}")
Get architecture overview before proposing changes:
get_architecture("project")
Trace call paths to understand bug propagation:
trace_call_path("buggy_function", "entry_point")
| Operation | Raw Reading | Graph Query | Savings |
|-----------|-----------|-------------|---------|
| Find all callers of function | ~50K tokens | ~700 tokens | 71x |
| Architecture overview | ~200K tokens | ~3K tokens | 67x |
| Impact analysis for PR | ~30K tokens | ~2K tokens | 15x |
| Find related tests | ~20K tokens | ~1.5K tokens | 13x |
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take vibeeval/knowledge-graph from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.