Agent skill · software engineering · abhigyanpatwari
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?\
Why this skill is useful
Adds specific commands and workflows for analyzing code dependencies and risks that the AI wouldn't reliably generate on its own.
What it needs
Requires gitnexus installed locally. About 4k tokens when loaded. Last updated 2026-08-06. 45,147 stars on the source repository.
What this skill does
Impact Analysis with GitNexus When to Use "Is it safe to change this function?" "What will break if I modify X?" "Show me the blast radius" "Who uses this code?" Before making non-trivial code changes Before committing — to understand what your changes affect Bind the repository first Impact analysis is the gate that authorizes an edit, so it must answer for the repository you are about to edit. Call listrepos {} before the first tool call. With one indexed repository, use the examples below as written. With more than one, pass repo on every call: an omitted repo normally errors, but under an MCP policy with a configured default it resolves to that default silently. If you cannot tell which repository is meant, stop and ask — every result below an ambiguous identity inherits the ambiguity. listrepos is paginated, so page with offset: pagination.nextOffset until hasMore is false before concluding a repository is absent. detectchanges takes worktree when your changes are in a linked worktree the MCP server was not launched from. The server auto-detects a worktree only when it was launched from inside one; otherwise git diff runs in the wrong checkout and reports zero changed symbols — a false clean check that carries none of the degradation flags described below. In the CLI fallbacks, --repo . means the current checkout; pass the intended repository path instead when you are not standing in it. State the bound identity with your risk report: Workflow If "Index is stale" → run node .gitnexus/run.cjs analyze in terminal. If .gitnexus/run.cjs is missing, replace node .gitnexus/run.cjs with npx gitnexus in the fallback commands. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills abhigyanpatwari/gitnexus-impact-analysis