Menu
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, graph schema, or workflow reference.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
| name | gitnexus-guide |
| description | Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, graph schema, or workflow reference. |
Quick reference for all GitNexus CLI commands, tools, and the knowledge graph schema.
IMPORTANT — How to use GitNexus: GitNexus is a standalone CLI tool. Run it directly via
gitnexus <command>in the Bash tool (e.g.,gitnexus query "auth flow",gitnexus impact "myFunc" --direction upstream). Do NOT usemcpl call gitnexus ...— gitnexus is not invoked through mcpl.
For any task involving code understanding, debugging, impact analysis, or refactoring:
gitnexus status — check index freshnessIf step 1 warns the index is stale, run
gitnexus analyzein the terminal first.
| 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 |
| Tools, schema reference | gitnexus-guide (this file) |
| Index, status, clean, wiki CLI commands | gitnexus-cli |
All commands are run directly via the Bash tool. Do not use mcpl.
| 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 par-term-emu-core-rust |
gitnexus context "<symbol>" --repo <name> | 360-degree symbol view — categorized refs, processes it participates in | gitnexus context "validateUser" --repo par-term-emu-core-rust |
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 par-term-emu-core-rust |
gitnexus detect-changes --repo <name> | Git-diff impact — what do your current changes affect | gitnexus detect-changes --repo par-term-emu-core-rust |
gitnexus rename "<old>" "<new>" --repo <name> | Multi-file coordinated rename with confidence-tagged edits | gitnexus rename "myFunc" "myNewFunc" --repo par-term-emu-core-rust |
gitnexus cypher "<query>" --repo <name> | Raw graph queries | gitnexus cypher "MATCH ..." --repo par-term-emu-core-rust |
gitnexus status | Index freshness check | gitnexus status |
gitnexus analyze | Build or refresh the index | gitnexus analyze |
gitnexus list | Discover indexed repos | gitnexus list |
Multi-repo note: This workspace has multiple repos indexed. Always pass
--repo <name>to every command to avoid "multiple repositories" errors.
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