Given a list of changed source files, returns which test files are affected — directly or transitively through the import graph. Use to answer: which tests should I run after this code change?

Finds the exact import chain that connects a changed source file to a test file. Use to answer: why does changing file X cause test Y to be affected? Returns the step-by-step import path from the test to the changed file.

Runs git diff --name-only <base_branch>...HEAD internally and returns affected test files. Use instead of get_affected_tests when you want the server to handle the git diff automatically.

Returns the direct import graph for a specific file: what it imports, and what imports it. Use to answer: what depends on this file? What does this file depend on?

Finds source files that are not reachable from any test file through the import graph — i.e. completely untested code. Use to answer: which parts of the codebase have zero test coverage?

Returns a bird's-eye view of the project's test structure: coverage rate, most-imported source files (highest risk to change), and tests with the deepest import chains. Use to answer: what is the overall test health of this project?

Finds source files that are never imported by any other file — dead code candidates safe to delete. Automatically excludes known entry points (index.ts, main.ts, pages/, routes/, app/, api/, bin/). Use to answer: which files in this codebase are orphaned and can be safely removed?

Detects circular import dependencies — A imports B which imports C which imports A. Cycles cause unpredictable module initialization order and indicate tight coupling. Use to answer: are there circular dependencies I need to break before refactoring?

Classifies each changed file as type-only or runtime, then splits affected tests into "must run" vs "skippable". A test is skippable when the changed file contains only TypeScript type declarations (interfaces/type aliases) or the test imports it via import type. Use to answer: which tests can I skip after a type-only refactor?

Compares a file against its HEAD version and classifies the change as breaking_api_change (exported function signature changed, parameter removed/added, interface field removed) or internal_refactor (only implementation body changed). Use to answer: is this PR a breaking change or a safe refactor?

Like get_affected_tests_by_branch, but correctly handles renamed and moved files. Uses --find-renames to detect file moves and --ignore-all-space to skip whitespace-only changes. Use instead of get_affected_tests_by_branch when the branch contains refactors or file moves.

Clears the cached AST for a project root, forcing a full re-parse on the next call. Use after switching branches, running git pull, or adding/removing files.

Retrieves a bidirectional or directed dependency graph mapped to individual declarations, functions, and variables.

Generates a token-optimized representation of a source file by stripping function and method bodies, keeping only JSDocs and declarations with line numbers.

Outputs the optimal test execution command for Jest, Vitest, or Playwright based on changed files.