Timwood0x10/CodeScope

tools

• build_evidence

  Build evidence findings by applying the rule set (sync/memory/error/pattern/framework/ffi) to the project's semantic_fact rows. Each rule declares fact needs + a combine mode (Collect / MissingMatch /

• build_project_state

  Build (or rebuild) and persist the project state snapshot. Runs the full v0.3 Evidence Pipeline (evidence aggregation + state queries) and UPSERTs the result into the project_state table. Returns the

• codescope_trace

  Interactive recursive call exploration (depth + direction) or shortest path.

• connected_components

  Connected components in the call graph.

• count_tokens

  Estimate token count (DeepSeek formula).

• detect_architecture_drift

  Check call edges for layer violations (Repository→Controller).

• detect_capability_drift

  Check declared capabilities have implementing entities.

• detect_changes

  Analyze impact of modified files: direct/indirect callers.

• detect_documentation_drift

  Check README language claims vs actual code entities.

• detect_drift

  Scan all declared capabilities & contracts for doc-vs-code drift.

• detect_ffi_boundaries

  Detect FFI boundaries (extern/C, JNI, WASM, C ABI).

• enhance_project

  Run background enhancement: full tree-sitter parse, call graph, FTS, and v0.3 semantic_fact extraction. Prerequisite for build_evidence to produce non-empty findings. Complexity metrics and n-gram sem

• explain_module

  Build module knowledge card: entities, capabilities, integrity score.

• explain_symbol

  Get comprehensive symbol info: definition, callers, callees, dependencies.

• find_callees

  Find what a function calls.

• find_callees_by_entity

  Find callees of a symbol by its graph entity id.

• find_callers

  Find who calls a function.

• find_callers_by_entity

  Find callers of a symbol by its graph entity id.

• find_definition

  [DEPRECATED — use find_symbol]

• find_references

  Find all locations referencing a symbol.

• find_symbol

  Recommended — find symbol by exact name (kind, file, line/col).

• force_index_files

  Force-index files/dirs bypassing default skip rules (test/, docs/, node_modules/, .gitignore, etc.).

• get_entry_points

  Find entry points (main/init/setup/run/handler).

• get_graph

  Retrieve the complete code graph in paginated pages.

• get_graph_stats

  Quick statistics: nodes, edges, files.

• get_module_tree

  Hierarchical module/directory tree.

• get_neighbors

  Fetch direct neighbors (callers + callees) of a graph node.

• get_project_state

  Get the previously persisted project state snapshot (without rebuilding). Returns the snapshot_json string for the project, or a JSON error object if no snapshot exists yet (run build_project_state fi

• get_routes

  Get registered HTTP routes (Gin/Echo/Chi/net/http).

• get_subgraph

  Fetch a local region centered on a node (1-hop).

• get_type_info

  Query type definitions (struct/enum/trait) with reference counts.

• get_verifier_registry_status

  Inspect the registered verifiers and their health (supported claim types, unsupported list, backend readiness).

• graph_query

  Cypher-like DSL query: MATCH (Function:main)-[Calls]->(Method).

• index_file

  Index a single source file.

• index_project

  Index a project directory: parse all source files, build IR, and construct the code graph.

• project_overview

  Primary — comprehensive project overview: languages, modules, symbols, entry points, analysis progress.

• search

  Recommended — unified search: FTS5 exact/prefix matching complemented by n-gram semantic vector search (restored in v0.2.5; lexical similarity, no external model) when results run short.

• search_code

  [DEPRECATED — use search]

• shortest_path

  Shortest call path between two functions (BFS).

• trace_flow

  Recursive execution flow tracing (caller→callee chain).

• verify_claim

  Verify a single claim (capability_exists / contract_holds / architecture_follows).

• verify_integrity

  Check README-promised features actually exist in code.

• verify_reality

  Verify a single AI statement against code evidence.

• verify_review

  Verify code review comment claims.

• verify_statement

  Verify a natural-language claim against the project's indexed evidence. Pipeline: IntentParser → Planner → EvidenceBuilder → VerdictBuilder. Returns JSON with verdict (Supported\

• verify_summary

  Parse natural-language summary and verify each claim.