lee/graphify
1
0
Fork 0
mirror of https://github.com/safishamsi/graphify.git synced 2026-07-13 02:47:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

after pipeline, offer to guide user through the graph

Browse Source
This commit is contained in:
Safi
2026-04-05 00:35:47 +01:00
parent 1cd52f191e
commit fa702bd69f
2 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
graphify/skill.md
+8
View File
@@ -626,6 +626,14 @@ Then paste these sections from GRAPH_REPORT.md directly into the chat:
Do NOT paste the full report - just those three sections. Keep it concise.
Then immediately offer to explore. Pick the single most interesting suggested question from the report - the one that crosses the most community boundaries or has the most surprising bridge node - and ask:
> "The most interesting question this graph can answer: **[question]**. Want me to trace it?"
If the user says yes, run `/graphify query "[question]"` on the graph and walk them through the answer using the graph structure - which nodes connect, which community boundaries get crossed, what the path reveals. Keep going as long as they want to explore. Each answer should end with a natural follow-up ("this connects to X - want to go deeper?") so the session feels like navigation, not a one-shot report.
The graph is the map. Your job after the pipeline is to be the guide.
---
## For --update (incremental re-extraction)
skills/graphify/skill.md
+8
View File
@@ -626,6 +626,14 @@ Then paste these sections from GRAPH_REPORT.md directly into the chat:
Do NOT paste the full report - just those three sections. Keep it concise.
Then immediately offer to explore. Pick the single most interesting suggested question from the report - the one that crosses the most community boundaries or has the most surprising bridge node - and ask:
> "The most interesting question this graph can answer: **[question]**. Want me to trace it?"
If the user says yes, run `/graphify query "[question]"` on the graph and walk them through the answer using the graph structure - which nodes connect, which community boundaries get crossed, what the path reveals. Keep going as long as they want to explore. Each answer should end with a natural follow-up ("this connects to X - want to go deeper?") so the session feels like navigation, not a one-shot report.
The graph is the map. Your job after the pipeline is to be the guide.
---
## For --update (incremental re-extraction)