From 7754bea9d412014a3ab18de0fe09905a348fa856 Mon Sep 17 00:00:00 2001 From: Davide Grilli Date: Tue, 17 Nov 2026 08:02:16 +0100 Subject: [PATCH] Aggiungi graphify: sezione in CLAUDE.md e graphify-out/ in .gitignore Co-Authored-By: Claude Sonnet 5.5 --- .gitignore | 3 +++ CLAUDE.md | 11 +++++++++++ 2 files changed, 14 insertions(+) diff --git a/.gitignore b/.gitignore index 3b6f533..ed72d7e 100644 --- a/.gitignore +++ b/.gitignore @@ -44,3 +44,6 @@ publish/ # Setup generato da Inno Setup (installer/PrepStep.iss) installer/Output/ __pycache__/ + +# graphify +graphify-out/ diff --git a/CLAUDE.md b/CLAUDE.md index 83fb067..b04603b 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -149,3 +149,14 @@ intercambiabili: - `CreoBom.cs` usa `AsmRecordReader` (parser esatto dei record binari, `docs/formato-asm-record.md`, condiviso con la GUI in fase 4) e risolve i sottoassiemi cercandoli in cartelle locali (`-p`), non contro `cad_index.db`. + +## graphify + +This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships. + +Rules: +- When graphify-out/graph.json exists, run `graphify query ""` before your first grep, search or source-file read for a codebase question, and put this rule in every subagent prompt that explores code. Read raw files only for lines the graph or an earlier read already located. Use `graphify path "" ""` for relationships and `graphify explain ""` for focused concepts. When the answer is under a Markdown heading, `graphify section ""` prints that section's text, so the .md need not be opened. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output. +- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing. +- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context. +- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost). +- A committed graphify-out/graph.json is rewritten whole on every build, so a large diff to it in a pull request is expected. Do not flag it as churn or suggest skipping the graph rebuild or its hooks.