From f61bb27d9c4261cc5f77d3a5da3c9910d031d183 Mon Sep 17 00:00:00 2001 From: Safi Date: Sun, 3 May 2026 17:23:31 +0100 Subject: [PATCH] Fix #688: stricter VS Code Copilot instructions to enforce GRAPH_REPORT.md first Co-Authored-By: Claude Sonnet 4.6 --- graphify/__main__.py | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/graphify/__main__.py b/graphify/__main__.py index ee67ebb1..596d8fe9 100644 --- a/graphify/__main__.py +++ b/graphify/__main__.py @@ -370,9 +370,17 @@ _VSCODE_INSTRUCTIONS_MARKER = "## graphify" _VSCODE_INSTRUCTIONS_SECTION = """\ ## graphify -Before answering architecture or codebase questions, read `graphify-out/GRAPH_REPORT.md` if it exists. -If `graphify-out/wiki/index.md` exists, navigate it for deep questions. -Type `/graphify` in Copilot Chat to build or update the knowledge graph. +For any question about this repo's architecture, structure, components, or how to add/modify/find +code, your **first tool call must be** to read `graphify-out/GRAPH_REPORT.md` (if it exists). + +Triggers: "how do I…", "where is…", "what does … do", "add/modify a ", +"explain the architecture", or anything that depends on how files or classes relate. + +After reading the report (and `graphify-out/wiki/index.md` for deep questions), answer from the +graph. Only read source files when (a) modifying/debugging specific code, (b) the graph lacks +the needed detail, or (c) the graph is missing or stale. + +Type `/graphify` in Copilot Chat to build or update the graph. """