codebase-memory-reference

Name: codebase-memory-reference
Availability: InStock
Author: pepsi1978

Reference Codebase Memory MCP tools, edge types, and graph query patterns.

1|Updated Feb 9, 2026

Search Tags:#codebase #mcp #memory #knowledge-graph #graph-queries #search_graph #query_graph

Ready to run

npx skills add https://github.com/Pepsi1978/proggs --skill codebase-memory-reference

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codebase-memory-reference
Source: https://github.com/Pepsi1978/proggs/tree/main/claude-code-setup/commands/codebase-memory-reference
Command: npx skills add https://github.com/Pepsi1978/proggs --skill codebase-memory-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebase Memory MCP Reference provides a centralized guide to memory-based codebase graph tooling, enabling quick discovery of tools, edge types, and query patterns needed to navigate large codebases.

Core Features & Use Cases

Tool cataloging (index_repository, index_status, list_projects, delete_project)
Edge and node semantics coverage (CALLS, IMPORTS, DEFINES, HANDLES, etc.)
Example-driven guidance for search_graph and query_graph usage in real projects.

Quick Start

Ask for a codebase memory MCP reference by name and specify the tool or edge type you want to explore.

Frequently Asked Questions about codebase-memory-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I query a codebase knowledge graph to find function calls and imports?▼

You query a codebase knowledge graph using Cypher-like patterns with search_graph and query_graph to traverse edge types like CALLS and IMPORTS. This returns contextual code retrieval results by navigating defined node relationships across indexed repositories.

What edge types are available when navigating a codebase memory graph?▼

Codebase memory graph edge types include CALLS, IMPORTS, DEFINES, and HANDLES for mapping semantic relationships. These edges connect node labels to represent structural dependencies and execution paths within the indexed repository knowledge graph.

How do I index a repository for codebase memory graph queries?▼

You index a repository by invoking the index_repository tool, then monitor progress with index_status. Once indexing completes, the codebase memory graph supports search_graph queries and code retrieval across the indexed project structure.

Can I manage multiple codebase memory projects and delete outdated ones?▼

Yes, the codebase memory MCP tool suite provides list_projects to enumerate indexed repositories and delete_project to remove outdated ones. This manages the knowledge graph scope to ensure precise graph queries across active codebases.

What is the best way to retrieve specific code using graph primitives in a large codebase?▼

The best way to retrieve code in a large codebase is using query_graph with documented Cypher-like patterns to target specific node labels and edge types. This narrows search_graph results to precise contextual code segments based on structural relationships.

Why do my codebase memory graph queries return empty or inaccurate results?▼

Graph queries return empty results when search_graph patterns are not aligned with the documented Tools list, Edge Types, Node Labels, and Cypher-like syntax. Matching the exact API set and graph primitives ensures contextual code retrieval from the indexed repository.