GitNexus plugin for Grok Build

Name: GitNexus
Author: abhigyanpatwari

Community Claude Code plugin, installs in GrokPluginDevelopment

GitNexus: The Zero-Server Code Intelligence Engine

How to install GitNexus in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add abhigyanpatwari/GitNexus

2. Install the plugin:

grok plugin install gitnexus@abhigyanpatwari/GitNexus --trust

✓ Install-checked in Grok Buildchecked Oct 18, 2026

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add abhigyanpatwari/GitNexus, then select gitnexus and press i.

Command format: Grok Build's plugin guide

Runs a local MCP server (with npx, uvx or similar), so that tool needs to be installed, for example Node.js for npx.

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 12 skills. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (12)

gitnexus-cli — Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
gitnexus-debugging — Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
gitnexus-exploring — Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
gitnexus-guide — Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
gitnexus-impact-analysis — Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
gitnexus-lfg — Use when the user wants the GitNexus engineering pipeline run end-to-end on a task: gitnexus-plan (plan depth chosen up front), a blocking gate to execute with gitnexus-work or stop, finishing with a gitnexus-review of the result. Examples:
gitnexus-pdg-query — Use when querying or extending GitNexus's PDG control/data-dependence surface (the `pdg_query` MCP tool, CDG/REACHING_DEF edges), or reasoning about "what controls X" / "where does Y flow" / guard clauses. Examples: "what guards this statem
gitnexus-plan — Use when you need a deep, implementation-ready engineering plan for a code change — built from GitNexus graph intelligence, statement-level PDG analysis, and targeted source verification, compact enough that an implementation agent can star
gitnexus-refactoring — Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
gitnexus-review — Review code changes with GitNexus from a GitHub PR URL or number, a branch/ref or commit range, or local staged, unstaged, and untracked changes. Use when the user asks for a code review, merge-risk assessment, regression hunt, missing-test
gitnexus-taint-analysis — Use when working on, reviewing, or extending GitNexus's CFG/taint/PDG subsystem (the `--pdg` layers), or when reasoning about source→sink data-flow findings. Examples: "How does taint analysis work here?", "Why didn't explain find this flow
gitnexus-work — Use when executing an engineering plan produced by gitnexus-plan (or a small bounded task directly) — implements step by step with GitNexus impact checks before every symbol edit, tests from the plan's scenarios, and detect_changes gating e

MCP servers (1)

gitnexus — stdio server

Hooks (1)

hooks — PostToolUse, PreToolUse

About this listing

GitNexus is a community plugin on GitHub by abhigyanpatwari, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 12 skills, 1 MCP server, 1 hook. No license stated in the repo, so check with the author before reusing its code. We checked commit 565e50276dc9. It's one of 409 listings in the Development category on GrokStacks.

GitNexus FAQ

How do I install GitNexus in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add abhigyanpatwari/GitNexus, then run grok plugin install gitnexus@abhigyanpatwari/GitNexus --trust. Then start a new Grok session, or press r in /plugins, to load it.

Is GitNexus an official Grok Build plugin?

No. GitNexus is a community plugin on GitHub by abhigyanpatwari, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does GitNexus include?

According to what Grok loaded in our install check, GitNexus includes 12 skills, 1 MCP server, 1 hook: gitnexus-cli, gitnexus-debugging, gitnexus-exploring, gitnexus-guide, gitnexus-impact-analysis, gitnexus-lfg….

Details

Type: Plugin
Category: Development
Source: Community Claude Code plugin, installs in Grok
License: No license stated
Author: abhigyanpatwari
Source repo: https://github.com/abhigyanpatwari/GitNexus
Checked commit: 565e50276dc9
Homepage: https://gitnexus.vercel.app
Checked by GrokStacks: Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain GitNexus? Add the badge; it links to this page.

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/gitnexus/)

HTML

<a href="https://grokstacks.com/p/gitnexus/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

GitNexusCommunity plugin for Grok Build · 12 skills, 1 MCP server, 1 hookGitNexus: The Zero-Server Code Intelligence EngineView on GrokStacks →

<a href="https://grokstacks.com/p/gitnexus/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">GitNexus</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 12 skills, 1 MCP server, 1 hook</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">GitNexus: The Zero-Server Code Intelligence Engine</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[GitNexus on GrokStacks](https://grokstacks.com/p/gitnexus/)**: Community plugin for Grok Build with 12 skills, 1 MCP server, 1 hook. Install: `grok plugin install gitnexus@abhigyanpatwari/GitNexus --trust` (after `grok plugin marketplace add abhigyanpatwari/GitNexus`)

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Development

Abap2UI5

Build UI5 Apps Purely in ABAP

Community Claude Code plugin, installs in GrokPluginDevelopment

Accessibility Agents

Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating inaccessible code.

Community Claude Code plugin, installs in GrokPluginDevelopment