Audit Tools

Sweep the entire codebase for drift, duplication, dead code, and regression risk. All Audit tools are Pro — free tier receives a preview with partial results to demonstrate value.

get_vision_gaps

Question it answers: "What's specified but not built? What's built but not specified?"

Finds specs without matching code AND complex code without matching specs. Useful for keeping PRDs and implementation in sync.

When to use: During sprint planning, to find unimplemented specs. During cleanup, to find undocumented code.

Parameters:

• repo (required): Repository name

• module (optional): Filter to a specific module

get_cross_repo_audit

Question it answers: "Are shared dependencies drifting between repos?"

Compares two repositories for code duplication, structural overlap, diverged shared modules, and shared environment variables.

When to use: When maintaining multiple repos that share code. When evaluating whether to consolidate.

Parameters:

• repo (required): First repository name

• target_repo (required): Second repository name to compare against

get_consolidation_opportunities

Question it answers: "Where is duplicate or overlapping logic?"

Finds duplicate code (by function body hash), parallel consumers of the same data, competing DB access patterns, and functions with identical signatures in different modules.

When to use: Before a refactor pass. When reducing codebase surface area. When investigating why the same bug appears in multiple places.

Parameters:

• repo (required): Repository name

• module (optional): Filter to a specific module

get_unused_code

Question it answers: "What code is never called and safe to delete?"

Finds functions unreachable from any production entry point. Uses dual verification: graph reachability AND text-reference backup. Returns three tiers:

• Dead: Graph-unreachable AND no text references. Safe to delete.

• Likely Dead: Graph-unreachable BUT found as text in other files. May be string-dispatched.

• Alive: Graph-reachable. Not reported.

When to use: During cleanup passes. After a refactor. When reducing bundle size.

Parameters:

• repo (required): Repository name

• module (optional): Filter to a specific module

get_test_coverage

Question it answers: "Which modules and functions lack tests?"

Per-module coverage summary showing which files have tests, which high-complexity functions lack them, and overall coverage distribution.

When to use: When deciding where to add tests. During code review, to verify new code has test coverage.

Parameters:

• repo (required): Repository name

• module (optional): Filter to a specific module

get_regression_risk

Question it answers: "How risky is this change to production?"

Scores functions by likelihood of breaking production based on: cyclomatic complexity, call-graph exposure (number of callers), recent churn (change frequency), and caller count across modules.

When to use: Before deploying changes. During PR review, to assess risk. When prioritizing what to test.

Parameters:

• repo (required): Repository name

• module (optional): Filter to a specific module

• function (optional): Specific function to score