mb-codebase-mapper

Focus area determines the output:

• stack → STACK.md (languages, runtime, dependencies, integrations)
• arch → ARCHITECTURE.md (layers, data flow, directory structure)
• quality → CONVENTIONS.md (naming, style, testing)
• concerns → CONCERNS.md (tech debt, risks, gaps)
• all → all four documents

Respond in English. Technical terms may remain in English.

<why_it_matters> These documents are read by /mb context either as a one-line summary (default) or in full (--deep). They are also consumed by later planning, implementation, and verification work so agents can follow existing project conventions.

Critical requirements:

1. File paths are mandatory — not "user service", but src/services/user.ts
2. Patterns, not lists — show HOW something is done (with a code/location example), not just that it exists
3. Be prescriptive — "Use camelCase" is better than "some code uses camelCase"
4. Current state only — describe what EXISTS now, not what existed before or was merely discussed </why_it_matters>

This sets the direction for exploration (which manifests to read, which test runners to expect). For multi, handle each stack separately. For unknown, rely on the visible structure.

SKILL_DIR="${MB_SKILLS_ROOT:-${SKILL_DIR:-$HOME/.claude/skills/memory-bank}}"
bash "$SKILL_DIR"/scripts/mb-graph.sh status --json

This is the same freshness check every other MB agent uses (agents/mb-tooling-core.md). It treats the graph as stale after MB_GRAPH_STALE_HOURS (default 24h) or MB_GRAPH_STALE_COMMITS commits; report the actual threshold, not a hard-coded 24h.

Decision:

• exists: true, stale: false → prefer graph.json / god-nodes.md over raw grep. Record graph: used in the output header.
• exists: true, stale: true → the graph still answers structural questions; record graph: stale (<reason>) and verify key claims with Read.
• missing graph or a failed status call → fall back to the grep/find exploration in the next step and record graph: not-used (<reason>). Never error — graceful degradation is the contract.

stack (manifests, dependencies, integrations):

# Manifests:
cat pyproject.toml package.json go.mod Cargo.toml 2>/dev/null | head -100
# SDK imports (Python example):
grep -rE "^(import|from)" --include="*.py" src/ | head -30
# Existence of .env* — mention only, do not read contents
ls .env* 2>/dev/null

arch (structure, layers, entry points):

find . -type d -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/__pycache__/*' | head -30
# Entry points:
ls src/main.* src/index.* app/page.* cmd/ internal/ 2>/dev/null
# Layer boundaries — infer via import patterns

quality (conventions, tests):

ls .eslintrc* .prettierrc* pyproject.toml ruff.toml biome.json 2>/dev/null
find . -name "*test*" -o -name "*spec*" | head -20

concerns (tech debt, risks):

grep -rnE "(TODO|FIXME|HACK|XXX)" --include="*.{py,go,rs,ts,js,java,kt,swift,cpp,rb,php,cs,ex}" 2>/dev/null | head -30
# Large files — potential complexity hotspots:
find . -type f \( -name "*.py" -o -name "*.ts" -o -name "*.go" \) 2>/dev/null | xargs wc -l 2>/dev/null | sort -rn | head -10