| name | gitnexus-guide |
| description | Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?" |
GitNexus Guide
Quick reference for all GitNexus MCP tools, resources, and the knowledge graph schema.
Always Start Here
For any task involving code understanding, debugging, impact analysis, or refactoring:
- Read
gitnexus://repo/{name}/context — codebase overview + check index freshness
- Match your task to a skill below and read that skill file
- Follow the skill's workflow and checklist
GitNexus is read-only — every tool and resource here only reads the index; none write tracked files (no rename, no wiki, no skill/doc regeneration). See the Read-Only Analysis Policy in CLAUDE.md / AGENTS.md.
If step 1 warns the index is stale, rebuilding is not routine — only run npx gitnexus analyze --skip-agents-md when the task genuinely needs it, then git status and git checkout -- any tracked file it touched (see gitnexus-cli).
If gitnexus_query returns empty for a known repo, npx gitnexus index . registers it in the global registry (writes only ~/.gitnexus, no tracked files).
Skills
| Task | Skill to read |
|---|
| Understand architecture / "How does X work?" | gitnexus-exploring |
| Blast radius / "What breaks if I change X?" | gitnexus-impact-analysis |
| Trace bugs / "Why is X failing?" | gitnexus-debugging |
| Plan a refactor (read-only impact/refs) | gitnexus-refactoring |
| Verify a diff / PR — what did I affect? | gitnexus-review |
| Custom graph queries (cycles, metrics) | gitnexus-query |
| Tools, resources, schema reference | gitnexus-guide (this file) |
| Index status / list / register (read-only) | gitnexus-cli |
Tools Reference
| Tool | What it gives you |
|---|
query | Process-grouped code intelligence — execution flows related to a concept |
context | 360-degree symbol view — categorized refs, processes it participates in |
impact | Symbol blast radius — what breaks at depth 1/2/3 with confidence |
detect_changes | Git-diff impact — what do your current changes affect |
cypher | Raw graph read queries (read gitnexus://repo/{name}/schema first) |
list_repos | Discover indexed repos |
Resources Reference
Lightweight reads (~100-500 tokens) for navigation:
| Resource | Content |
|---|
gitnexus://repo/{name}/context | Stats, staleness check |
gitnexus://repo/{name}/clusters | All functional areas with cohesion scores |
gitnexus://repo/{name}/cluster/{clusterName} | Area members |
gitnexus://repo/{name}/processes | All execution flows |
gitnexus://repo/{name}/process/{processName} | Step-by-step trace |
gitnexus://repo/{name}/schema | Graph schema for Cypher |
Graph Schema
Nodes: File, Function, Class, Interface, Method, Community, Process
Edges (via CodeRelation.type): CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, MEMBER_OF, STEP_IN_PROCESS
MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"})
RETURN caller.name, caller.filePath
