Quick update on claude-bootstrap for those following along. The biggest pain point we kept hitting: Claude Code burns tokens reading files and grepping around just to find where a function lives. On larger codebases it gets really slow and loses context fast. v2.7.0 adds a tiered code graph that’s fully automated. Run /initialize-project and it now: Downloads and installs codebase-memory-mcp (single binary, zero deps) Indexes your entire codebase into a persistent knowledge graph Configures MCP so Claude queries the graph instead of reading files Enables auto-indexing + installs a post-commit hook to keep it fresh Claude Code with claude bootstrap would now use search_graph instead of grep, trace_call_path instead of chasing imports, and detect_changes for blast radius before touching shared code. ~90% fewer tokens for navigation. The 3 tiers Tier 1: codebase-memory-mcp covers AST graph, symbol lookup, blast radius and is always on. Tier 2: Joern CPG (CodeBadger): Full CPG — AST + CFG + PDG, data flow and is opt-in Tier 3: CodeQL with Interprocedural taint analysis, security and is Opt-In During init, Claude Code asks which tier you want. Tier 1 is always on. Tiers 2 and 3 install automatically if you pick them — Joern via Docker, CodeQL via brew/binary. What “graph first, file second” means in practice: The new code-graph skill teaches Claude Code to:
- Query the graph before opening any file 2. Check blast radius before modifying shared code 3. Trace call paths instead of manually reading imports 4. Only read full files when it actually needs to edit them There’s also a cpg-analysis skill for Tier 2/3 that covers when to use control flow graphs, data dependency analysis, and taint tracking. Everything is fully automated: /initialize-project handles it end-to-end - binary download, MCP config, initial index, auto-indexing config, git hooks. GitHub: github.com/alinaqi/claude-bootstrap Let me know what you think. submitted by /u/naxmax2019
Originally posted by u/naxmax2019 on r/ClaudeCode