Exploratory Toolkit

Use the exploratory commands when you want to answer one dependency question quickly, without building or changing a config. They read the same dependency graph the config runner uses, but print ad-hoc results instead of enforcing rules.

These commands are ideal for refactoring, debugging, and understanding unfamiliar code.

Commands

Command	Answers
entry-points	What are the roots of the project?
files	Which files does this entry point pull in?
imported-by	Who directly imports this file?
resolve	Is there a path from an entry point to this file or package?
circular	Are there circular dependencies?
node-modules	Which packages are used, unused, missing, or installed?
lines-of-code	How much effective code is there?
debug	What does rev-dep parse, resolve, and discover internally?

Shared conventions

• Most commands accept -c, --cwd to run against a different directory.
• Graph-building commands accept --follow-monorepo-packages to trace across workspace package boundaries, plus --package-json, --tsconfig-json, and --condition-names to control resolution.
• Glob arguments are matched relative to --cwd. Quote them ('**/*.test.ts') so your shell does not expand them first.

See Common investigative workflows for recipes that chain these commands together.