gitnexus-guide_skill

Overview

This skill documents GitNexus tools, resources, and the knowledge graph schema for repository-level code intelligence. It is the single reference for which MCP tools to run, where to read lightweight resources, and how to query the graph. Use this guide to map common tasks to the right GitNexus skill and to learn the available CLI/query primitives.

How this skill works

The guide lists available MCP tools (query, context, impact, detect_changes, rename, cypher, list_repos) and links them to concrete outputs you can inspect. It describes lightweight resource endpoints you can open (context, clusters, processes, schema) and includes the core graph node and edge types plus a simple example Cypher snippet. Start by checking repository context for index freshness, then pick the skill that matches your goal.

When to use it

• When you need to choose the correct GitNexus tool for architecture, debugging, impact analysis, or refactoring.
• Before running deep queries: to check repository index freshness via the context endpoint.
• When you want quick, consumable resource pages like clusters, processes, or the repo schema.
• To discover what graph nodes and relations exist before writing raw Cypher queries.
• When assessing the blast radius of changes using detect_changes or impact.

Best practices

• Always read gitnexus://repo/{name}/context first and run npx gitnexus analyze if the index is stale.
• Match your task to a specific skill (exploring, debugging, refactoring, impact analysis) and follow that skill’s workflow.
• Use lightweight resource endpoints (clusters, processes, schema) for focused facts before running broad queries.
• Prefer tool-level primitives (query, context, impact) for common analyses and reserve cypher for custom graph queries.
• When renaming, use the rename tool to apply coordinated, confidence-tagged edits across files.

Example use cases

• Investigate why a function is failing: open the process or context page, then run query or debugging skill.
• Estimate blast radius of a proposed API change: run impact or detect_changes against your diff.
• Perform a large-scale rename: use the rename tool then validate with context and detect_changes.
• Explore execution flows for a feature: open processes, follow STEP_IN_PROCESS edges, or run the query tool for grouped flows.
• Write a custom graph query: read gitnexus://repo/{name}/schema, then run cypher with the provided node/edge types.