How do I install the Gitnexus Guide skill?

Run npx skillmds@latest add mindfold-ai/gitnexus-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gitnexus Guide safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gitnexus Guide?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gitnexus Guide free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gitnexus Guide?

mindfold-ai (@mindfold-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gitnexus Guide by mindfold-ai — Agent Skill

Name: Gitnexus Guide
Rating: 4.2 (5 reviews)
Author: mindfold-ai

Gitnexus Guide

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?"

mindfold-ai b81900b 3.5 KB Updated Sep 9, 2026

File contents

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 node .gitnexus/run.cjs analyze in 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.filePath

---name: gitnexus-guidedescription: 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: 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 `node .gitnexus/run.cjs analyze` in 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 ```cypher MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"}) RETURN caller.name, caller.filePath ```

Frequently asked questions