Indexes a codebase into a knowledge graph of symbols, calls and dependencies, so your coding agent can answer how code works, what a change will break and why a bug happens. Ask in plain language instead of grepping through files.
@abhigyanpatwariUse when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki,…
@abhigyanpatwariUse when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where…
@abhigyanpatwariUse when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of…
@abhigyanpatwariUse when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or…
@abhigyanpatwariUse when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples:…
@abhigyanpatwariUse when the user wants the GitNexus engineering pipeline run end-to-end on a task: gitnexus-plan (plan depth chosen up front), a…
@abhigyanpatwariUse when querying or extending GitNexus's PDG control/data-dependence surface (the `pdg_query` MCP tool, CDG/REACHING_DEF edges),…
@abhigyanpatwariUse when you need a deep, implementation-ready engineering plan for a code change — built from GitNexus graph intelligence,…
@abhigyanpatwariRun a GitNexus production-readiness pull request review using a coordinated reviewer swarm.
@abhigyanpatwariUse when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\",…
@abhigyanpatwariReview code changes with GitNexus from a GitHub PR URL or number, a branch/ref or commit range, or local staged, unstaged, and…
@abhigyanpatwariUse when working on, reviewing, or extending GitNexus's CFG/taint/PDG subsystem (the `--pdg` layers), or when reasoning about…
@abhigyanpatwariGitNexus branch hygiene and mergeability reviewer. Use to classify merge state, conflicts, stale branches, merge-from-main…
@abhigyanpatwariGitNexus docs and Definition-of-Done reviewer. Use to translate repo guidance, linked issues, changed domains, docs requirements,…
@abhigyanpatwariGitNexus PR facts and repository-history investigator. Use to gather PR identity, visible GitHub state, changed files, commits,…
@abhigyanpatwariGitNexus production-risk reviewer. Use for risk-model-first review of changed files, runtime behavior, multi-domain changes, user…
@abhigyanpatwariGitNexus security and trust-boundary reviewer. Use for auth, permissions, secrets, injection, unsafe parsing, external input…
@abhigyanpatwariGitNexus final review synthesis critic. Use to check whether the final PR review is evidence-grounded, risk-prioritized,…
@abhigyanpatwariGitNexus test and CI reviewer. Use to verify whether changed behavior is covered by targeted tests, whether CI actually runs…
@abhigyanpatwariIs this you? Claim your profilePut a plugin at the top of Plugins, from $9
