graphify Checked

tag who wrote it

/graphify add <url> --contributor "Name" # tag who added it to the corpus

/graphify query "<question>" # BFS traversal - broad context

/graphify query "<question>" --dfs # DFS - trace a specific path

/graphify query "<question>" --budget 1500 # cap answer at N tokens

/graphify path "AuthModule" "Database" # shortest path between two concepts

/graphify explain "SwinTransformer" # plain-language explanation of a node

## What graphify is for

Drop any folder of code, docs, papers, images, or video into graphify and get a queryable knowledge graph. Persistent across sessions, honest audit trail (EXTRACTED/INFERRED/AMBIGUOUS), community detection surfaces cross-document connections you wouldn't think to ask about.

## What You Must Do When Invoked

If the user invoked `/graphify --help` or `/graphify -h` (with no other arguments), print the contents of the `## Usage` section above verbatim and stop. Do not run any commands, do not detect files, do not default the path to `.`. Just print the Usage block and return.

**Fast path — existing graph:** Before doing anything else, check whether `graphify-out/graph.json` exists. The expected location is `graphify-out/graph.json` relative to the **current working directory** (i.e. the project root where you are running commands). If it exists AND the user's request is a natural-language question about the codebase (e.g. "How does X work?", "What calls Y?", "Trace the data flow through Z") and NOT an explicit rebuild command (`--update`, `--cluster-only`, or a bare path/URL that implies fresh extraction): **skip Steps 1–5 entirely and jump straight to `## For /graphify query`.** Run `graphify query "<question>"` immediately. Do not run detect. Do not check corpus size. Do not ask the user to narrow. The graph is already built — use it.

If no path was given, use `.` (current directory). Do not ask the user for a path.

If the path argument starts with `https://github.com/` or `http://github.com/`, treat it as a GitHub URL - run Step 0 before anything else, then continue with the resolved local path.

Follow these steps in order. Do not skip steps.

### Step 0 - GitHub repos and multi-path merge (only if a URL or several paths)

Only when the path is one or more `https://github.com/...` URLs, or several local subfolders to merge. See `references/github-and-merge.md` for the clone, cross-repo merge, and monorepo flow, then continue with the resolved local path. A plain local path skips this step.

### Step 1 - Ensure graphify is installed

Detect the correct Python interpreter (handles uv tool, pipx, venv, system installs)

PYTHON=""

GRAPHIFY_BIN=$(which graphify 2>/dev/null)

1. uv tool installs — most reliable on modern Mac/Linux

if [ -z "$PYTHON" ] && command -v uv >/dev/null 2>&1; then

_UV_PY=$(uv tool run --from graphifyy python -c "import sys; print(sys.executable)" 2>/dev/null)

if [ -n "$_UV_PY" ]; then PYTHON="$_UV_PY"; fi

fi

2. Read shebang from graphify binary (pipx and direct pip installs)

if [ -z "$PYTHON" ] && [ -n "$GRAPHIFY_BIN" ]; then

_SHEBANG=$(head -1 "$GRAPHIFY_BIN" | tr -d '#!')

case "$_SHEBANG" in

*[!a-zA-Z0-9/_.@-]*) ;;

*) "$_SHEBANG" -c "import graphify" 2>/dev/null && PYTHON="$_SHEBANG" ;;

esac

fi

3. Fall back to python3

if [ -z "$PYTHON" ]; then PYTHON="python3"; fi

if ! "$PYTHON" -c "import graphify" 2>/dev/null; then

if command -v uv >/dev/null 2>&1; then

uv tool install --upgrade graphifyy -q 2>&1 | tail -3

_UV_PY=$(uv tool run --from graphifyy python -c "import sys; print(sys.executable)" 2>/dev/null)

if [ -n "$_UV_PY" ]; then PYTHON="$_UV_PY"; fi

else

"$PYTHON" -m pip install graphifyy -q 2>/dev/null \

|| "$PYTHON" -m pip install graphifyy -q --break-system-packages 2>&1 | tail -3

fi

fi

Write interpreter path for all subsequent steps (persists across invocations)

mkdir -p graphify-out

"$PYTHON" -c "import sys; open('graphify-out/.graphify_python', 'w', encoding='utf-8').write(sys.executable)"

Save scan root so `graphify update` (no args) knows where to look next time.

The scan path is passed through a quoted heredoc, never substituted into the

command line itself: a bare `cd <path>` (or an unquoted heredoc, which

still expands $()/backticks in its body) would let a malicious path execute

as shell code the moment this line runs.

"$PYTHON" -c "import os, sys; out_path = os.path.abspath('graphify-out/.graphify_root'); os.chdir(sys.stdin.readline().rstrip('\n')); open(out_path, 'w', encoding='utf-8').write(os.getcwd())" <<'GRAPHIFY_ROOT_EOF'

INPUT_PATH

GRAPHIFY_ROOT_EOF

If the import succeeds, print nothing and move straight to Step 2.

**In every subsequent bash block, replace `python3` with `$(cat graphify-out/.graphify_python)` to use the correct interpreter.**

### Step 2 - Detect files

$(cat graphify-out/.graphify_python) -c "

import json

from graphify.detect import detect

from pathlib import Path

from graphify.paths import out_path

from graphify.watch import _read_build_excludes, _read_build_gitignore

result = detect(Path('INPUT_PATH'), extra_excludes=_read_build_excludes(out_path()), gitignore=_read_build_gitignore(out_path()))

#