chore: remove graphify #111

2026-08-17T11:18:10+07:00

sulthan commented

2026-08-17 11:18:10 +07:00

Removes the graphify integration. It was measured against this repo rather than assumed.

Why

graphify query returns a keyword-seeded BFS neighbourhood, not a location. Asked where CORS origin reflection is implemented, it returned 73 nodes — mostly api_test.go helpers, plus a Reflection and Type Assertions section from .agents/skills/golang-performance/references/cpu.md matched on the word "reflection" — and never named httpmw/middleware.go:135 or main.go:121. grep returned both in 39ms. Same shape asking how the poller skips kagane: 145 nodes, top hits poller_test.go helpers and two nodes named T.

graphify explain "BrowserFetcher" is sound (browser.go L52, 9 EXTRACTED edges), but that is what lsp references already answers, against live files instead of a snapshot.

Staleness was never the problem — graph.json rebuilt 5s after f568fb5, so the git hooks worked. Retrieval quality was.

What it cost

Two PreToolUse hooks injecting a "MANDATORY: run graphify query first" paragraph into context on every grep/find and every source-file read.
685k input tokens across 5 build runs (cost.json).
3.4MB of graph.json + graph.html tracked, across 11 commits of map-refresh churn.

AGENTS.md is the stronger orientation artifact for a repo this size: it carries the CDP constraints, the UTC-clock finding, the per-site adapter list, and the security invariants — none of which an AST graph derives. Graphify earns its keep on repos too large to grep coherently and without curated docs; not this one.

Changes

Delete the committed map (graphify-out/, -58k lines).
Drop the ## graphify rules block from AGENTS.md (CLAUDE.md is a symlink, so both).
Drop the five graphify-out/* entries from .gitignore.
Empty the two PreToolUse hooks in .claude/settings.json.
Remove the stale graphify query instruction from .claude/skills/implement-tickets/SKILL.md — it pointed dispatched ticket-implementer agents at a binary that no longer exists.

Uninstalled outside the tree (not in this diff): the graphifyy CLI, ~/.claude/skills/graphify/, the global ~/.claude/CLAUDE.md block, the Bash(graphify query *) permission in the git-ignored .claude/settings.local.json, and the post-commit / post-checkout git hooks.

Verification

grep -ri graphify over the worktree is clean; remaining hits are inside .git/ (commit messages, two stale branch configs). No code touched — backend and userscript are untouched, so go test ./... is unaffected.

Removes the graphify integration. It was measured against this repo rather than assumed. ## Why `graphify query` returns a keyword-seeded BFS neighbourhood, not a location. Asked where CORS origin reflection is implemented, it returned 73 nodes — mostly `api_test.go` helpers, plus a `Reflection and Type Assertions` section from `.agents/skills/golang-performance/references/cpu.md` matched on the word "reflection" — and never named `httpmw/middleware.go:135` or `main.go:121`. `grep` returned both in 39ms. Same shape asking how the poller skips kagane: 145 nodes, top hits `poller_test.go` helpers and two nodes named `T`. `graphify explain "BrowserFetcher"` is sound (`browser.go L52`, 9 `EXTRACTED` edges), but that is what `lsp references` already answers, against live files instead of a snapshot. Staleness was never the problem — `graph.json` rebuilt 5s after `f568fb5`, so the git hooks worked. Retrieval quality was. ## What it cost - Two `PreToolUse` hooks injecting a "MANDATORY: run graphify query first" paragraph into context on **every** grep/find and every source-file read. - 685k input tokens across 5 build runs (`cost.json`). - 3.4MB of `graph.json` + `graph.html` tracked, across 11 commits of map-refresh churn. `AGENTS.md` is the stronger orientation artifact for a repo this size: it carries the CDP constraints, the UTC-clock finding, the per-site adapter list, and the security invariants — none of which an AST graph derives. Graphify earns its keep on repos too large to grep coherently and without curated docs; not this one. ## Changes - Delete the committed map (`graphify-out/`, -58k lines). - Drop the `## graphify` rules block from `AGENTS.md` (`CLAUDE.md` is a symlink, so both). - Drop the five `graphify-out/*` entries from `.gitignore`. - Empty the two `PreToolUse` hooks in `.claude/settings.json`. - Remove the stale `graphify query` instruction from `.claude/skills/implement-tickets/SKILL.md` — it pointed dispatched ticket-implementer agents at a binary that no longer exists. Uninstalled outside the tree (not in this diff): the `graphifyy` CLI, `~/.claude/skills/graphify/`, the global `~/.claude/CLAUDE.md` block, the `Bash(graphify query *)` permission in the git-ignored `.claude/settings.local.json`, and the `post-commit` / `post-checkout` git hooks. ## Verification `grep -ri graphify` over the worktree is clean; remaining hits are inside `.git/` (commit messages, two stale branch configs). No code touched — backend and userscript are untouched, so `go test ./...` is unaffected.

sulthan added 1 commit 2026-08-17 11:18:11 +07:00

chore: remove graphify d168cf1ad0

Measured on this repo, graphify cost more than it returned. `graphify query`
answers with a keyword-seeded BFS neighbourhood, not a location: asking where
CORS origin reflection lives returned 73 nodes, mostly api_test.go helpers
plus an unrelated golang-performance doc section matched on the word
"reflection", and never named httpmw/middleware.go:135 or main.go:121 — which
grep gives in 40ms. `graphify explain` on a known symbol is sound but
duplicates what the LSP already answers against live files.

Against that, the PreToolUse hooks injected a "run graphify query first"
paragraph on every grep and every source read, the map cost 685k input tokens
across five builds, and graph.json plus graph.html carried 3.4MB through 11
commits of churn. AGENTS.md is the better orientation artifact: it holds the
CDP and clock findings, the adapter list, and the security invariants, none of
which an AST graph can derive.

Removes the committed map, the AGENTS.md rules block, the .gitignore entries,
both hooks, and the stale `graphify query` instruction in the
implement-tickets skill. The CLI, its skill directory, and the post-commit /
post-checkout git hooks were uninstalled outside the tree.

sulthan merged commit 3ac865cd08 into main

2026-08-17 11:43:16 +07:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sulthan/mangaBookmark#111