메뉴
Incrementally update the Graphify graph after code changes — re-extract only the touched directories and re-merge, instead of a full rebuild. Use after a commit, after editing modules, or when graphify-out is stale. Aliases - graphify-update, refresh-graph, regraph.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Semantic memory layer for long-term knowledge storage and retrieval across sessions. Use for /agentmemory remember, search, context, forget, status commands. Distinct from holographic memory (live cross-agent state) — agentmemory is a searchable knowledge base backed by BM25+vector hybrid search at localhost:3111.
Alias for /consult-ring261T. Consult Ring 2.6 1T (inclusionai/ring-2.6-1t) on OpenRouter. Use when user says "/ask-ring261T" or "ask ring".
Use when tracing how a pick on findtorontoevents.ca/audit got there — what source emitted it, which gates it passed or was rejected by, why it is or is not in Smart Picks / High Conviction / Money Ready, or why a class shows the win-rate it does. Also for "which DB tables matter", per-asset-class pick-funnel case studies, and onboarding someone to the audit pipeline.
Use when user asks to check GitHub Actions for failing jobs, chronic cancellations, or jobs without a subsequent successful run. Also for CI/CD health audits, rerunning failed workflows, or monitoring workflow reliability. Aliases - checkGHA, gha_health, github_actions_health, gh_actions, check_actions, fixjob, github_actions, actions_health
Get a second opinion from OpenAI Codex via its headless CLI. Use when the user says "/consult-codex", "ask codex", "codex second opinion", or wants an outside model's take on a question, plan, or code.
Get a second opinion from Cursor Agent via its headless CLI (the `agent` command). Use when the user says "/consult-cursor-agent", "ask cursor-agent", "cursor-agent second opinion", or wants an outside model's take on a question, plan, or code.
| name | graphify-refresh |
| description | Incrementally update the Graphify graph after code changes — re-extract only the touched directories and re-merge, instead of a full rebuild. Use after a commit, after editing modules, or when graphify-out is stale. Aliases - graphify-update, refresh-graph, regraph. |
A full /graphify-map rebuild of this 20K-file repo is slow. After code
changes, re-extract only the affected directories and re-merge.
PY="$(cat graphify-out/.graphify_python)"
GRAPH_REPORT.md records the build commit ("Built from commit: <sha>").
Compare to git rev-parse HEAD. If equal and no uncommitted edits, the graph
is current — stop.
git diff --name-only HEAD~1 HEAD -- '*.py' | sed 's|/[^/]*$||' | sort -u
For uncommitted work use git diff --name-only (no range). Keep only
directories that were part of the original map (see /graphify-map source-dir
list) — ignore node_modules, tests, .worktrees, vendored dirs.
for d in <changed dirs>; do
"$PY" -m graphify update "$d" --no-cluster 2>&1 | grep -E 'Rebuilt|updated in'
done
graphify update is content-hash cached — unchanged files are skipped, so this
is fast even on a big directory. It rewrites <dir>/graphify-out/graph.json.
graphify watch <path> is the auto-mode (rebuilds on file save) — mention it to
the user if they want continuous refresh, but for a one-shot update use update.
The repo-level graphify-out/graph.json is a manual merge of every per-dir
fragment (the merge-graphs CLI is broken on 0.8.3). Re-run the manual merge
from /graphify-map Step 3 over ALL */graphify-out/graph.json fragments, then:
"$PY" -m graphify cluster-only . --no-viz --graph graphify-out/graph.json
If cluster-only warns "new graph has N nodes but existing has M, refusing to
overwrite", the rebuild legitimately shrank (deleted code) — re-run with
GRAPHIFY_FORCE=1 or --force.
graphify update handles code only. Changed .md/docs need semantic
re-extraction — re-run tools/_graphify_docs_multibackend.py (it is per-file
cached, so only changed docs cost tokens).
State which directories were re-extracted, the new node/edge counts, and the commit the graph now reflects.
/graphify-map — full rebuild from scratch/graphify-ask — query the graph