Conversation
🌱 graft blast radius2 areas changed → 6 areas can be affected. 14 dependent symbols, depth 2. flowchart TB
A0(("Workspace Graph<br/>5 symbols"))
A1(("CLI Engine<br/>4 symbols"))
A2(("Pull Request Review<br/>2 symbols"))
A3(("Context Check<br/>1 symbol"))
A4(("Claude Hooks<br/>1 symbol"))
AX(("1 smaller area<br/>1 symbol"))
classDef reached fill:#D9EDF3,stroke:#3AA7C9,stroke-width:1.5px,color:#0E313C;
class A0,A1,A2,A3,A4 reached;
classDef tail fill:#EEF2F3,stroke:#9AA4A9,stroke-width:1px,color:#3A4247;
class AX tail;
Who knows this code — 4 people across 8 areas
Ownership is git history over each area's own files, weighted towards recent work (120-day half-life). Merge commits and bots are dropped, and you are dropped from your own PR. A name with no All 14 dependent symbols, grouped by areaWorkspace Graph — 5 symbols in 5 files
CLI Engine — 4 symbols in 2 files
Pull Request Review — 2 symbols in 2 files
Context Check — 1 symbol in 1 file
Claude Hooks — 1 symbol in 1 file
MCP Tools — 1 symbol in 1 file
Test signal per changed area — 1 ✓ · 1 –Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.
35 test suites also reference this code38 symbols, kept out of the diagram and the table so they cannot crowd out the areas a reviewer has to look at.
Open the interactive graph → — click an area to see its dependent symbols at file:line. |
Summary
Adds Gleam to Graft's generic tree-sitter graph tier.
.gleamfiles in context and structural graph buildsValidation
npm run buildnpm testgleam-lang/gleamrepository: 227 Gleam files, 936 Gleam symbols, and 388 Gleam-related edges extracted without parser errors