coograph: Skill for Claude Code

Rebuild or incrementally update the .code-graph/graph.db SQLite database.

IMPORTANT: This skill runs commands. Follow every step in order. Do not skip error handling.

---

Step 1: Locate the code-graph tooling

Find server.py — it could be in several locations depending on the project setup:

.github/code-graph/server.py          # standard location
coograph/.github/code-graph/server.py  # monorepo with template as submodule

Search for it:

find . -path "*/code-graph/server.py" -not -path "*/node_modules/*" 2>/dev/null | head -5

If not found: stop and tell the user:

"No code-graph tooling found. Run the coograph-init skill to set it up, or copy .github/code-graph/ from the coograph."

If multiple found: use the one closest to the current working directory (shortest path). Report which one you're using.

Store the resolved path as $SERVER_PY.

Step 2: Check Python

python3 --version 2>/dev/null || python --version 2>/dev/null

If neither works: stop and tell the user Python 3.10+ is required.

If version is below 3.10: stop and tell the user Python 3.10+ is required.

Store the working Python command as $PYTHON (python3 preferred over python).

Step 3: Determine build mode

• If the user said "update" or "incremental" → use --update
• If the user said "build", "rebuild", "full", or gave no argument → use --build
• If .code-graph/graph.db does not exist → always use --build (update requires an existing db)

Step 4: Run the build

Execute from the project root (the directory where .code-graph/ should be created):

cd <project-root> && $PYTHON $SERVER_PY <--build or --update>

Expected success output includes lines like:

• Detected stacks: java, structured
• Graph built: N files -> .code-graph/graph.db (X.XXs)

or for update:

• Graph updated: updated N, dependents M, deleted D
• Graph up to date — no changes detected.

Step 5: Verify

Confirm the database exists and has data: