gitnexus-guide

Map coding tasks to GitNexus tools and resources for graph queries.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill gitnexus-guide-leonardo-corte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-guide
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/.claude/skills/gitnexus/gitnexus-guide
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill gitnexus-guide-leonardo-corte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users need a quick, accurate reference for GitNexus capabilities—so they can query the code knowledge graph, understand available tools/resources, and follow the right workflow when investigating or refactoring code.

Core Features & Use Cases

  • One-place tool and resource reference: Quickly map common tasks (understand, trace, analyze impact, refactor) to the specific GitNexus skill to read.
  • Knowledge-graph navigation guidance: Directs users to start with gitnexus://repo/{name}/context, plus supporting navigation resources like clusters, processes, and schema.
  • Tool capability breakdown: Explains what each MCP-like tool returns, including query, context, impact, detect_changes, rename, cypher, and list_repos.

Quick Start

Ask the AI to “Explain which GitNexus tools I should use to trace how a function is called and what would break if I change it,” then follow the tool and resource mapping from this guide.

Frequently Asked Questions about gitnexus-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query a code knowledge graph for impact analysis?

To perform impact analysis on a code knowledge graph, start with repository context, then use the impact tool to trace what would break if you change a specific function or component.

What is the best way to navigate a repository knowledge graph for debugging?

Navigating a repository knowledge graph for debugging requires starting with the repo context resource, then applying the query and detect_changes tools to trace execution flow and identify faulty logic.

Can I use Cypher queries to understand code structure in GitNexus?

Yes, you can use the cypher tool to execute schema-aware queries against the indexed repository knowledge graph to retrieve detailed code structure and dependency relationships.

How do I map refactoring tasks to the correct code intelligence tools?

Mapping refactoring tasks involves using the rename tool to update references and the context tool to review surrounding clusters, ensuring schema-aware graph queries validate the changes.

Do I need to start with repo context before using graph tools?

Yes, starting with repo context is required before using other graph tools, as it establishes the baseline repository state needed to query clusters, processes, and schema accurately.

What does the detect_changes tool return when analyzing code?

The detect_changes tool identifies modifications within the indexed repository knowledge graph, allowing you to see exactly what code elements have been altered for impact analysis.