What problem it solves

Developers and coding agents need to understand how code is connected before making changes. GitNexus provides a graph-based view of symbols, callers, dependencies and execution flows to support code discovery, impact analysis and refactoring.

Key features

• Graph-based code intelligence — Index a codebase as a knowledge graph covering symbols, calls, dependencies and execution flows. Query it through MCP tools, the CLI or a web graph explorer.

  Source: README

• Impact and dependency analysis — Inspect callers and dependencies, assess what a change could affect, and review the impact of a Git diff through the provided analysis tools.

  Source: README

• Flow tracing and semantic rename — Trace paths between symbols and preview or apply semantic renames from the command line or agent tools.

  Source: README

• Editor and agent integration — Configure MCP for supported editors and have the analysis command install agent skills, register Claude Code hooks and create repository context files.

  Source: README

• Web graph explorer and portable indexes — Browse indexed repositories and use AI chat through the web UI without re-uploading or re-indexing code. Index artifacts can also be stored outside the checkout, with configurable source-content retention.

  Source: README

Quick start

Copied verbatim from the project's README.

# Run from your repository root
npx gitnexus analyze

# Connect your editors once
npx gitnexus setup

gitnexus setup -c cursor,codex

gitnexus analyze                 # Refresh the current repository's index
gitnexus analyze --watch         # Reindex as local files change
gitnexus query "authentication"  # Search the graph
gitnexus impact UserService --direction upstream
gitnexus status                  # Check index freshness
gitnexus list                    # List indexed repositories
gitnexus serve                   # Serve indexed repositories to the web UI

Who it may suit

This may suit developers, coding-agent users and teams that need to explore code relationships or assess change impact. The supported editor integrations and command-line workflows may also suit teams establishing repository-aware tooling.

Topics to discuss

• Which editor or coding-agent workflow would benefit most from graph-based repository analysis?

• How should GitNexus communicate index freshness, coverage limits and ambiguous symbol resolution?

• Which additional language constructs or integrations should be prioritized for the knowledge graph?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/abhigyanpatwari/GitNexus#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.