agentleFS
VKirillVKirill/agent-consult/skills/gitnexus-guide/SKILL.md

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

The file

Files
SKILL.md

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:

  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

TaskSkill 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 / refactorgitnexus-refactoring
Tools, resources, schema referencegitnexus-guide (this file)
Index, status, clean, wiki CLI commandsgitnexus-cli

Tools Reference

ToolWhat it gives you
queryProcess-grouped code intelligence — execution flows related to a concept
context360-degree symbol view — categorized refs, processes it participates in
impactSymbol blast radius — what breaks at depth 1/2/3 with confidence
detect_changesGit-diff impact — what do your current changes affect
renameMulti-file coordinated rename with confidence-tagged edits
cypherRaw graph queries (read gitnexus://repo/{name}/schema first)
list_reposDiscover indexed repos

Resources Reference

Lightweight reads (~100-500 tokens) for navigation:

ResourceContent
gitnexus://repo/{name}/contextStats, staleness check
gitnexus://repo/{name}/clustersAll functional areas with cohesion scores
gitnexus://repo/{name}/cluster/{clusterName}Area members
gitnexus://repo/{name}/processesAll execution flows
gitnexus://repo/{name}/process/{processName}Step-by-step trace
gitnexus://repo/{name}/schemaGraph 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

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.