hooks
Load this when the user asked to install the post-commit hook or wire graphify into a project's AGENTS.md.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Load this when the user asked to install the post-commit hook or wire graphify into a project's AGENTS.md.
Agent definition
hooks.mdgraphify reference: commit hook and native AGENTS.md integration
Load this when the user asked to install the post-commit hook or wire graphify into a project's AGENTS.md.
For git commit hook
Install a post-commit hook that auto-rebuilds the graph after every commit. No background process needed - triggers once per commit, works with any editor.
graphify hook install # install graphify hook uninstall # remove graphify hook status # check
After every `git commit`, the hook detects which code files changed (via `git diff HEAD~1`), re-runs AST extraction on those files, and rebuilds `graph.json` and `GRAPH_REPORT.md`. Doc/image changes are ignored by the hook - run `/graphify --update` manually for those.
If a post-commit hook already exists, graphify appends to it rather than replacing it.
---
For native AGENTS.md integration
Run once per project to make graphify always-on in your agent sessions:
graphify agents install
This writes a `## graphify` section to the local `AGENTS.md` that instructs your agent to check the graph before answering codebase questions and rebuild it after code changes. No manual `/graphify` needed in future sessions.
graphify agents uninstall # remove the section
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Other agents on graphify.
- add-watch
Load this when the user ran `/graphify add <url>` or passed `--watch`. Neither is part of the default build.
Open agent - exports
Load this when the user passed one of the export flags (`--wiki`, `--neo4j`, `--neo4j-push`, `--falkordb`, `--falkordb-push`, `--svg`, `--graphml`, `--mcp`), or when the corpus is large enough for the token-reduction benchmark. Each step runs only for its own flag.
Open agent - extraction-spec
Load this in Step 3 Part B when the corpus has at least one doc, paper, or image chunk. A pure-code corpus skips Part B and never reads this file. Each semantic subagent receives the prompt below verbatim (substitute FILE_LIST, CHUNK_NUM, TOTAL_CHUNKS, DEEP_MODE, and CHUNK_PATH).
Open agent - github-and-merge
Load this when the user passed one or more `https://github.com/...` URLs, or named several local subfolders to merge into one graph.
Open agent - query
Load this when the user asks a question against an existing graph, or runs `/graphify path` or `/graphify explain`. The core's query stub points here for the full traversal flow. These flows use the `graphify query` CLI when it is available and fall back to an inline NetworkX
Open agent - transcribe
Load this only when `detect` reported one or more `video` files. A corpus with no video never reads this.
Open agent

