graph-build
Build Code Knowledge Graph
Build or update the .gauntlet/graph.db knowledge graph
for the current codebase.
Steps
-
Detect target: Use the current working directory or a user-specified path.
-
Check for existing graph: If
.gauntlet/graph.dbexists, run an incremental update. Otherwise, run a full build. -
Run the build script:
For full build:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/graph_build.py <dir>For incremental update:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/graph_build.py <dir> --incremental -
Report results: Show the JSON output including files parsed, nodes created, edges created, and duration.
-
Suggest next steps: Recommend searching the graph or running blast radius analysis.
When To Use
- At the start of a session to build structural awareness
- After significant code changes to update the graph
- Before running blast radius analysis or flow tracing
- When the user asks about codebase structure
What Gets Parsed
The graph extracts nodes (File, Class, Function, Type, Test) and edges (CALLS, IMPORTS_FROM, INHERITS, CONTAINS, IMPLEMENTS, TESTED_BY) from 20+ languages including Python, JavaScript, TypeScript, Go, Rust, Java, C/C++, Ruby, and PHP.
Storage
- Database:
.gauntlet/graph.db(SQLite with WAL mode) - Auto-creates
.gauntlet/.gitignoreto prevent commits - Incremental updates use SHA-256 hashing to skip unchanged files
More from athola/claude-night-market
project-planning
Turn a specification into a phased implementation plan with dependency ordering.
111code-quality-principles
KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity and preventing over-engineering.
82project-brainstorming
Guide project ideation through Socratic questioning to generate actionable project briefs with alternative comparisons.
80doc-generator
Generate or remediate documentation with human-quality writing and style
67rigorous-reasoning
Prevent sycophantic reasoning via checklist enforcing evidence-based conclusions and honest analysis.
66project-specification
Transform project briefs into testable specifications with user stories, acceptance criteria, and measurable outcomes.
66