Reference for GitNexus MCP tools, resources, and graph schema. Use when: asking what GitNexus tools exist, how to query the graph, or for MCP resource / schema reference. Not for: CLI commands (use dhpk-gitnexus-cli), task flows (use dhpk-gitnexus-exploring / dhpk-gitnexus-debugging / dhpk-gitnexus-impact-analysis / dhpk-gitnexus-refactoring). Output: the right tool / resource / skill to use next.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add hmj1026/dhpk --skill dhpk-gitnexus-guide --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dhpk Gitnexus Guide?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hmj1026-dhpk-gitnexus-guide)More formats (shields.io, HTML) on the badges page.
---
name: dhpk-gitnexus-guide
description: "Reference for GitNexus MCP tools, resources, and graph schema. Use when: asking what GitNexus tools exist, how to query the graph, or for MCP resource / schema reference. Not for: CLI commands (use dhpk-gitnexus-cli), task flows (use dhpk-gitnexus-exploring / dhpk-gitnexus-debugging / dhpk-gitnexus-impact-analysis / dhpk-gitnexus-refactoring). Output: the right tool / resource / skill to use next."
metadata:
dhpk-invocation-class: "implicit-eligible"
---
# 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:
1. **Read `gitnexus://repo/{name}/context`** — codebase overview + check index freshness
2. **Match your task to a skill below** and **read that skill file**
3. **Follow the skill's workflow and checklist**
> If step 1 warns the index is stale, run `npx gitnexus analyze` in the terminal first.
## Skills
| Task | Skill to read |
| -------------------------------------------- | ------------------- |
| Understand architecture / "How does X work?" | `dhpk-gitnexus-exploring` |
| Blast radius / "What breaks if I change X?" | `dhpk-gitnexus-impact-analysis` |
| Trace bugs / "Why is X failing?" | `dhpk-gitnexus-debugging` |
| Rename / extract / split / refactor | `dhpk-gitnexus-refactoring` |
| Tools, resources, schema reference | `dhpk-gitnexus-guide` (this file) |
| Index, status, clean, wiki CLI commands | `dhpk-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
```cypher
MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"})
RETURN caller.name, caller.filePath
```
## When NOT to Use
- You want to run index / wiki CLI commands → `dhpk-gitnexus-cli`
- You have a concrete task (understand / impact / debug / refactor) → read that specific gitnexus skill
- The repo has no GitNexus index yet → run `npx gitnexus analyze` first (see `dhpk-gitnexus-cli`)
## Output
A pointer to the correct GitNexus tool, resource, or sibling skill for the user's goal — plus the `gitnexus://repo/{name}/...` resource to read first.
## Verification
- [ ] `gitnexus://repo/{name}/context` read first (index fresh)
- [ ] Task matched to the right tool / skill in the tables above
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!