abhigyanpatw ari · Agent Skills
11 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.
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\"
- 1h installs
- 1
- GitHub stars
- 48.6K
- Updated
- Nov 17
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\"
- 1h installs
- 1
- GitHub stars
- 48.6K
- Updated
- Nov 17
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\"
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
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?\"
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
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-lfg Add retry support to the ingestion pipeline\", \"run the gitnexus pipeline on this\", \"plan, build and review this feature\".
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
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 start without re-investigating. Also strengthens existing plans via Deepen mode. Examples: "/gitnexus-plan Add retry support to the ingestion pipeline", "/gitnexus-plan deepen docs/plans/ .md", "plan this change using the knowledge graph".
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
gitnexus-pr-swarm-review
Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
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\"
- 1h installs
- 1
- GitHub stars
- 48.6K
- Updated
- Nov 17
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 analysis, or a verdict on whether a PR, branch, commit range, or local diff is safe.
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
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?\", \"Add a new sink/source\", \"Review the interprocedural taint code\".
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
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 detectchanges gating every commit. Examples: "/gitnexus-work docs/plans/2026-07-11-gitnexus-plan-ingestion-retry.md", "/gitnexus-work" (latest plan), "execute the plan".
- 1h installs
- 1
- GitHub stars
- 48.3K
- Updated
- Nov 4
