| name | gitnexus-guide |
| description | Use when the user asks about GitNexus itself — available commands, how to query the knowledge graph, graph schema, or workflow reference. Examples: "What GitNexus commands are available?", "How do I use GitNexus?" |
GitNexus Guide
IMPORTANT — How to use GitNexus: GitNexus is a standalone CLI tool. Run it directly
via gitnexus <command> in the Bash tool. Do NOT use mcpl call gitnexus ... or
npx gitnexus ... — gitnexus is installed globally and invoked by name.
Multi-repo note: Always pass --repo <name> to every command that operates on a
specific repo to avoid "multiple repositories" errors.
Quick reference for all GitNexus CLI commands and the knowledge graph schema.
Always Start Here
For any task involving code understanding, debugging, impact analysis, or refactoring:
- Run
gitnexus status — check index freshness
- Match your task to a skill below and read that skill file
- Follow the skill's workflow and checklist
If step 1 warns the index is stale, run gitnexus analyze first.
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 |
| Rename / extract / split / refactor | gitnexus-refactoring |
| Commands, schema reference | gitnexus-guide (this file) |
| Index, status, clean, wiki CLI commands | gitnexus-cli |
CLI Commands Reference
All commands are run directly via the Bash tool. Do not use mcpl or npx.
| Command | What it gives you | Example |
|---|
gitnexus query "<concept>" --repo <name> | Process-grouped code intelligence — execution flows related to a concept | gitnexus query "auth flow" --repo <name> |
gitnexus context "<symbol>" --repo <name> | 360-degree symbol view — categorized refs, processes it participates in | gitnexus context "validateUser" --repo <name> |
gitnexus impact "<symbol>" --direction upstream --repo <name> | Symbol blast radius — what breaks at depth 1/2/3 with confidence | gitnexus impact "myFunc" --direction upstream --repo <name> |
gitnexus detect-changes --repo <name> | Git-diff impact — what do your current changes affect | gitnexus detect-changes --repo <name> |
gitnexus rename "<old>" "<new>" --repo <name> | Multi-file coordinated rename with confidence-tagged edits | gitnexus rename "myFunc" "myNewFunc" --repo <name> --dry-run |
gitnexus cypher "<query>" --repo <name> | Raw graph queries | gitnexus cypher "MATCH ..." --repo <name> |
gitnexus status | Index freshness check | gitnexus status |
gitnexus analyze | Build or refresh the index | gitnexus analyze |
gitnexus list | Discover indexed repos | gitnexus list |
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
