codebase-memory-context

Queries codebase-memory MCP for symbols, call graphs, and impact analysis to produce targeted code context.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill codebase-memory-context-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-memory-context
Source: https://github.com/vovanostm-public/multica/tree/main/workflow-bundles/multica-specops-v5/codex_skills/.agents/skills/codebase-memory-context
Command: npx skills add https://github.com/vovanostm-public/multica --skill codebase-memory-context-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on a large repository, broad grep-style searches waste time and miss structural relationships. This Skill retrieves structural codebase knowledge—symbols, call graphs, ownership, dependencies, and impact maps—through the codebase-memory MCP index so each workflow stage gets precise, justified code context. ## Core Features & Use Cases - Structural Code Queries: Looks up symbols, callers/callees, files, and modules through the codebase-memory MCP index instead of broad repository searches. - Impact Mapping: Maps impacted packages and boundaries, escalating cross-package impacts to the Technical Architect role. - Graceful Degradation: Falls back to targeted file reads when the MCP index is unavailable and records the degraded mode in the output. - Use Case: During a multi-stage spec-driven workflow, a stage needs to know which modules are affected by changing a shared utility function. This Skill queries the index, maps the impacted packages, and returns a typed context.codebase evidence package with confidence and handoff fields. ## Quick Start Ask the agent to gather structural codebase context for the current stage, including impacted symbols, callers, and package boundaries, using the codebase-memory index.

Frequently Asked Questions about codebase-memory-context

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

FAQPage Schema
How do I get structural codebase context without broad grep searches?▼

Query the codebase-memory MCP index for relevant symbols, callers, callees, files, and modules instead of running broad searches. The Skill checks index status first and returns selected code context with confidence scores and fallbacks.

What is codebase-memory MCP used for in a workflow?▼

codebase-memory MCP provides indexed structural knowledge about a repository, including symbols, call graphs, ownership, and dependencies. It lets workflow stages retrieve targeted code context quickly rather than scanning the whole repository each time.

What happens if the codebase-memory MCP index is unavailable?▼

The Skill degrades gracefully by falling back to targeted file reads and records the degraded mode in the context.index_status output field. The workflow continues, but the degraded state stays visible to downstream stages.

When does impact analysis get escalated to a Technical Architect?▼

Escalation happens when the impact map shows changes crossing a package boundary. The Skill maps impacted packages and boundaries explicitly, and cross-boundary impact triggers a handoff to the Technical Architect role.

What outputs does the codebase context stage produce?▼

It produces context.codebase, context.index_status, and impact.map as typed evidence. Every output also includes used_evidence, assumptions, blockers, confidence, and handoff fields when applicable.