gitnexus-guide
Skill1 starsChanged 5 months agoMITView on GitHub
Documents GitNexus itself — available tools, knowledge graph queries, MCP resources, graph schema, and workflow reference. Activated by GitNexus-related questions about tooling, usage, and capabilities.
11 other projects use a version of this, 11 of them edited.
Adopted by
Most recently taken up by
- eduardtomasek/agent-code-inteledited, first seen Nov 8, 2026
- pandich93/youtube-niche-finderedited, first seen Nov 1, 2026
- MarkChu-git/typesafe-mcpedited, first seen Nov 1, 2026
- metagit-ai/metagit-cliedited, first seen Oct 31, 2026
- ErrorNotFound808/claude-skillsedited, first seen Oct 8, 2026
- abhigyanpatwari/GitNexusedited, first seen Oct 8, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 11
- abhigyanpatwari/GitNexus★ 49k11% same
- ucsandman/DashClaw★ 31821% same
- kunwarVivek/mcp-github-project-manager★ 10521% same
- haoxiang-xu/PuPu★ 3621% same
- pandich93/youtube-niche-finder★ 3321% same
- metagit-ai/metagit-cli★ 421% same
- MarkChu-git/typesafe-mcp★ 221% same
- vasceannie/slopgate★ 121% same
- AlexHercules/skills★ 089% same
- eduardtomasek/agent-code-intel★ 021% same
1 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- gitnexus-cliSkill
- gitnexus-debuggingSkill
- gitnexus-exploringSkill
- gitnexus-impact-analysisSkill
- gitnexus-pr-reviewSkill
- gitnexus-refactoringSkill
- my-complex-skillSkill
The file
Files
Usage
Loaded automatically when its description matches the active task. The body below provides the working context.
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
If step 1 warns the index is stale, run
npx gitnexus analyzein the terminal 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 |
| Tools, resources, schema reference | gitnexus-guide (this file) |
| Index, status, clean, wiki CLI commands | 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 |
rename | Multi-file coordinated rename with confidence-tagged edits |
cypher | Raw graph 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.filePathDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

