gitnexus://repo/{name}/context

Codebase overview with stats, staleness check, and available tools

Resource URI

gitnexus://repo/{name}/context

name · string · required

Repository name from gitnexus://repos

Description

Returns a comprehensive overview of a specific repository, including:

• Project name and statistics
• Index staleness detection (if repo has new commits)
• Available tools and resources
• Re-indexing instructions

This is typically the first resource you read after discovering repos.

Returns

project · string

Repository name

staleness · string

Human-readable staleness hint (only present if index is stale)

Example: "Index is 3 commits behind HEAD. Run: npx gitnexus analyze"

stats · object

Codebase statistics

Show properties

files · number

Number of indexed files

symbols · number

Total code symbols (functions, classes, methods, etc.)

processes · number

Detected execution flows

tools_available · array

List of MCP tools with descriptions

• query — Process-grouped code intelligence
• context — 360-degree symbol view
• impact — Blast radius analysis
• detect_changes — Git-diff impact analysis
• rename — Multi-file coordinated rename
• cypher — Raw graph queries
• list_repos — Discover all indexed repositories

re_index · string

Command to re-index if data is stale

resources_available · array

List of available MCP resources for this repo

When to Use

• After discovering repos: Check overview and staleness
• Before starting work: Verify index is up-to-date
• Understanding scope: See how large the codebase is
• Feature discovery: Learn what tools and resources are available

Example Response

Fresh Index

project: my-app

stats:
  files: 342
  symbols: 1248
  processes: 87

tools_available:
  - query: Process-grouped code intelligence (execution flows related to a concept)
  - context: 360-degree symbol view (categorized refs, process participation)
  - impact: Blast radius analysis (what breaks if you change a symbol)
  - detect_changes: Git-diff impact analysis (what do your changes affect)
  - rename: Multi-file coordinated rename with confidence tags
  - cypher: Raw graph queries
  - list_repos: Discover all indexed repositories

re_index: Run `npx gitnexus analyze` in terminal if data is stale

resources_available:
  - gitnexus://repos: All indexed repositories
  - gitnexus://repo/my-app/clusters: All functional areas
  - gitnexus://repo/my-app/processes: All execution flows
  - gitnexus://repo/my-app/cluster/{name}: Module details
  - gitnexus://repo/my-app/process/{name}: Process trace

Stale Index

project: my-app

staleness: "Index is 3 commits behind HEAD. Run: npx gitnexus analyze"

stats:
  files: 342
  symbols: 1248
  processes: 87

tools_available:
  - query: Process-grouped code intelligence (execution flows related to a concept)
  - context: 360-degree symbol view (categorized refs, process participation)
  - impact: Blast radius analysis (what breaks if you change a symbol)
  - detect_changes: Git-diff impact analysis (what do your changes affect)
  - rename: Multi-file coordinated rename with confidence tags
  - cypher: Raw graph queries
  - list_repos: Discover all indexed repositories

re_index: Run `npx gitnexus analyze` in terminal if data is stale

resources_available:
  - gitnexus://repos: All indexed repositories
  - gitnexus://repo/my-app/clusters: All functional areas
  - gitnexus://repo/my-app/processes: All execution flows
  - gitnexus://repo/my-app/cluster/{name}: Module details
  - gitnexus://repo/my-app/process/{name}: Process trace

Staleness Detection

GitNexus automatically detects if the index is behind the current git HEAD:

• Compares indexed commit hash with current HEAD
• Counts commits between indexed state and HEAD
• Provides actionable re-indexing hint

If staleness is present, re-index before performing analysis to ensure accurate results.

Next Steps

After reading this resource:

1. Check Staleness

   If staleness warning appears, run npx gitnexus analyze to update the index

2. Explore Structure

   Read gitnexus://repo/{name}/clusters or gitnexus://repo/{name}/processes to understand the codebase

3. Use Tools

   Start using tools like query, context, or impact for analysis

Clusters Resource

Explore functional areas

Processes Resource

View execution flows