Compare commits

..

3 Commits

Author SHA1 Message Date
a620906209 df1b5bed9b Merge pull request 'chore(graphify): CLAUDE.md 新增 graphify 使用規則' (#80) from chore/graphify-claude-integration into master
Deploy Production / deploy (push) Successful in 1m31s
Run Tests / test (push) Successful in 37s
Reviewed-on: #80
2026-10-29 09:42:27 +00:00
a620906209 1958c3f01a chore(graphify): 新增 Claude Code 搜尋與讀檔 hook 設定
Run Tests / test (pull_request) Successful in 33s
由 graphify 安裝流程寫入,Bash/Grep/Read/Glob 執行前
會呼叫 graphify hook-guard 提示改用圖譜查詢。

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-29 17:41:37 +08:00
a620906209 6dfa36c1cb chore(graphify): CLAUDE.md 新增 graphify 使用規則
由 graphify 安裝流程寫入,要求查詢程式碼問題時先用 graphify query,
改完程式碼後執行 graphify update。

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-29 17:41:37 +08:00
2 changed files with 37 additions and 0 deletions
+26
View File
@@ -0,0 +1,26 @@
{
"hooks": {
"PreToolUse": [
{
"matcher": "Bash|Grep",
"hooks": [
{
"type": "command",
"command": "C:/Users/2110062/AppData/Roaming/uv/tools/graphifyy/Scripts/graphify.exe hook-guard search",
"timeout": 10
}
]
},
{
"matcher": "Read|Glob",
"hooks": [
{
"type": "command",
"command": "C:/Users/2110062/AppData/Roaming/uv/tools/graphifyy/Scripts/graphify.exe hook-guard read",
"timeout": 10
}
]
}
]
}
}
+11
View File
@@ -213,3 +213,14 @@
- 發現問題直接說,不要繞彎
- 有不確定的地方,明確標注「我不確定,需要你確認」
- 不要重複確認已經決定的技術選擇
## 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 "<question>"` 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 "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. 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.