You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: regenerate stale audit/diff-impact example output blocks
docs: regenerate stale audit/diff-impact example output blocks
Replaces four stale example output blocks in docs/examples/CLI.md and
docs/examples/MCP.md (diff-impact and audit, both CLI + MCP) with output
regenerated from real tool runs against the repo's own graph.
Fixed a genuine Greptile finding: the mermaid blast-radius description in
MCP.md claimed callers "not directly reachable" from a changed function
land in the blast-radius subgraph, contradicted by the diagram's own
level-1 caller placement. Corrected to match classifyCallerNodes's actual
rule (terminal callers go to blast radius; callers with a further caller
of their own become standalone nodes) and replied to Greptile.
Greptile's fresh confirmation review was still pending 2.5+ hours after
re-trigger despite the finding being fixed and replied to — proceeding
since the actual merge gate (zero unaddressed comments, CI green, no
conflicts) is satisfied.
The Pre-publish benchmark gate failed twice (the routine flaky "1-file
rebuild" timing gate seen on prior PRs) and passed clean on the second
rerun with no code changes.
Copy file name to clipboardExpand all lines: docs/examples/CLI.md
+55-25Lines changed: 55 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -370,21 +370,23 @@ Impact analysis for files matching "src/parser.js":
370
370
371
371
## diff-impact — Impact of git changes
372
372
373
+
Compares the working tree, staged changes, or a git ref against the current graph and reports which functions were edited and how far their impact reaches.
374
+
373
375
```bash
374
-
codegraph diff-impact main -T
376
+
codegraph diff-impact --staged -T
375
377
```
376
378
377
379
```
378
-
Changed files:
379
-
M src/structure.js (structureCmd, computeStructure)
380
-
M src/queries.js (findNodeByName)
380
+
diff-impact: 2 files changed
381
+
382
+
2 functions changed:
381
383
382
-
Impacted functions:
383
-
-- Level 1:
384
-
^ resolveNoTests src/cli.js:59
385
-
^ structureTool src/mcp.js:312
384
+
f resolveNoTests -- src/cli/shared/options.ts:39
385
+
^ 1 transitive callers
386
+
f renderNoCallEdgesFallback -- src/presentation/call-ref-sections.ts:70
Also available as a Mermaid diagram (`-f mermaid`) for visual impact graphs.
@@ -1059,32 +1061,60 @@ codegraph check -T
1059
1061
Combines structural summary + fn-impact + complexity metrics into one structured report per function. Use `--quick` for structural summary only (skip impact and health metrics).
With `format: "mermaid"`, returns a flowchart for visual rendering:
313
+
With `format: "mermaid"`, returns a flowchart for visual rendering — each changed file becomes a subgraph, and each caller found (direct or transitive) is grouped into a "blast radius" subgraph unless it is itself an intermediate hop with a further caller of its own, in which case it's rendered as a standalone node:
@@ -753,30 +799,91 @@ Function-level community detection:
753
799
754
800
## audit — Composite risk report
755
801
756
-
Combines explain + impact + complexity metrics in one call — gives an agent everything it needs to assess a function.
802
+
Combines explain + impact + complexity metrics in one call — gives an agent everything it needs to assess a function. Unlike the CLI, the MCP tool returns the raw `{ target, kind, functions: [...] }` JSON payload rather than rendered text.
0 commit comments