callidescope-trace

Running callidescope and reading what it says

Callidescope builds one call graph for a TypeScript workspace and measures the shape of it. It follows calls through injected dependencies — the hop from this.someService.load() into SomeService.load — which is the edge no file-at-a-time tool can see, and where most of a framework codebase's control flow actually lives.

Three commands, answering three different questions:

npx callidescope                                        # the whole workspace
npx callidescope depth --addresses src/foo.service.ts#FooService.bar    # one callable, vertically
npx callidescope breadth --addresses src/foo.service.ts#FooService.bar  # one callable, horizontally

A repository with no configuration file is traced with defaults rather than told to write one, so a bare run always produces something. What a run gates on and what it writes are both opt-in and both live in the callidescope-configure skill; this one is about reading the result.

callidescope: the whole workspace

Reports four findings.

Deep call stacks. The single deepest path below each entry point, when it exceeds limits.maximumDepth. Only one path per entry point is ever built, so a wide graph costs no more than a narrow one.

Module spread. A callable whose transitive callees reach many unrelated modules and which calls several of them directly. Both conditions matter: transitive reach alone flags every entry point, because an entry point legitimately reaches the whole program. A spread row is therefore specifically a callable personally orchestrating unrelated concerns.

Breadth. How many callables one callable calls directly. Reported always; gated only when limits.maximumBreadth is set, which is the one limit with no default.

Possibly misplaced callables. A callable whose callers nearly all sit in one other module of the same project. The output is a concrete move.

Reading a stack

Stack #1 | 🚨 [DEPTH ≥ 10 > 6] (decorated-method)
🚀 SomeCommand.run(options: SomeOptions): Promise<void> [.../some.command.ts:220]
   ↳ Measure the repository and write every configured output.
  └─> SomeService.measure(args: MeasureArguments): Result [.../some.service.ts:115]
     ↳ Measure aggregated statistics for the provided directory.