vibepro-codebase-memorylisted

# VibePro Codebase Memory ## Purpose Use `codebase-memory-mcp` as an optional impact lens inside VibePro's Story / Gate DAG / PR evidence workflow. The tool helps identify related files, symbols, routes, call paths, and risk hints before deciding tests, review roles, and split boundaries. It is not product intent and it is not proof that a change works. ## When to Use Use this Skill when a VibePro task involves broad source changes, `src/pr-manager.js`, Gate DAG behavior, Agent Review, evidence lifecycle, workflow orchestration, API routes, auth/security, data/state handling, release operations, or any change where the affected code path is not obvious from the diff alone. Also use it when `vibepro pr prepare` reports `pr_context.code_topology_context.available=true`, when the user asks about `codebase-memory-mcp`, or when Graphify alone is too coarse for changed-file impact analysis. Do not force it for tiny prose-only edits where no code path, reviewer scope, or test selection is in question. If the binary is missing or the repository is not indexed, record that as unavailable and continue with normal VibePro evidence. ## Operating Order 1. Confirm the current repository, branch, base ref, and Story ID. 2. Check provider availability: - `command -v codebase-memory-mcp` - `codebase-memory-mcp --version` - `codebase-memory-mcp cli list_projects '{}'` 3. If the current repository is missing from `list_projects`, index it before impact-sensitive work: - `cod