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
Copy file name to clipboardExpand all lines: .claude/skills/dogfood/SKILL.md
+14-21Lines changed: 14 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,17 @@ Your goal is to install the published package, exercise every feature, compare e
69
69
```
70
70
This should report `engine: native`. If it falls back to `wasm`, record why.
71
71
5. Record: platform, OS version, Node version, native binary package name + version, engine reported by `info`.
72
-
6.**Do NOT rebuild the graph yet.** The first phase tests commands against the codegraph source repo without a pre-existing graph.
72
+
6.**Update the native binary in the source repo.** The source repo's `node_modules` may have a stale native binary from a previous release. Since Phases 1–4 run commands against the source repo (using `--db` or directly), a version mismatch produces wrong results for **all phases**, not just benchmarks. Check and fix immediately:
Verify with `npx codegraph info` in the source repo. Revert `package.json` / `package-lock.json` changes after the session (do not commit them on the fix branch).
82
+
7.**Do NOT rebuild the graph yet.** The first phase tests commands against the codegraph source repo without a pre-existing graph.
73
83
74
84
---
75
85
@@ -202,30 +212,13 @@ Run all four benchmark scripts from the codegraph source repo and record results
202
212
203
213
### Pre-flight: verify native binary version
204
214
205
-
**Before running any benchmarks**, confirm the native binary in the source repo matches the version being dogfooded. A stale binary will produce misleading results (e.g., the Rust engine may lack features added in the release, causing silent WASM fallback during the complexity phase).
215
+
If you followed Phase 0 step 6, the source repo's native binary should already match `$ARGUMENTS`. Double-check before benchmarking:
206
216
207
217
```bash
208
-
# In the codegraph source repo — adjust the platform package name as needed:
2. Verify with `npx codegraph info` that the native engine loads at the correct version.
228
-
3. Revert the `package.json` / `package-lock.json` changes after benchmarking (do not commit them on the fix branch).
221
+
If it doesn't match, go back to Phase 0 step 6 and fix it — **all benchmark results with a stale binary are invalid.**
229
222
230
223
**Why this matters:** The native engine computes complexity metrics during the Rust parse phase. If the binary is from an older release that lacks this, the complexity phase silently falls back to WASM — inflating native complexity time by 50-100x and making native appear slower than WASM.
0 commit comments