abhigyanpatwari/gitnexus
9 skills7.6k installs406k starsGitHub
Install
npx skills add https://github.com/abhigyanpatwari/gitnexusSkills in this repo
1Gitnexus Impact AnalysisThe gitnexus-impact-analysis skill is designed for analyze code change impact across repositories with GitNexus dependency graphs. Invoke when the user analyzes change impact, dependency graphs, or cross-repo refactor risk.1.5kinstalls2Gitnexus ExploringThe gitnexus-exploring skill is designed for 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?\",. Invoke when the user the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.1.5kinstalls3Gitnexus RefactoringThe gitnexus-refactoring skill 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 Refactoring with GitNexus When to Use Rename this function safely Extract this into a module Split this service Move this to a new file Any task involving renaming extracting splitting or restructuring code Workflow 1 impact target X direction upstream Map all dependents 2 query search_query X Find execution flows involving X 3 context name X See all incoming outgoing refs 4 Plan update order interfaces implementations callers tests If Index is stale run node gitnexus run cjs analyze in terminal Checklists Rename Symbol rename symbol_name oldName new_name newName dry_run true preview all edits Review graph edits high confidence and ast_search edits review carefully If satisfied rename dry_run false apply edits detect_changes verify only expected files changed Run tests for affected processes Extract Module context name target see all incoming outgoing refs impact target direction1.4kinstalls4Gitnexus DebuggingThe gitnexus-debugging skill 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 Debugging with GitNexus When to Use Why is this function failing Trace where this error comes from Who calls this method This endpoint returns 500 Investigating bugs errors or unexpected behavior Workflow 1 gitnexus_query query error or symptom Find related execution flows 2 gitnexus_context name suspect See callers callees processes 3 READ gitnexus repo name process name Trace execution flow 4 gitnexus_cypher query MATCH path Custom traces if needed If Index is stale run npx gitnexus analyze in terminal Checklist Understand the symptom error message unexpected behavior gitnexus_query for error text or related code Identify the suspect function from returned processes gitnexus_context to see callers and callees Trace execution flow via process resource if applicable gitnexus_cypher for custom call chain traces if needed Read source files to confirm root cause Debugging Patterns Symptom GitNexus Approach Error message1.4kinstalls5Gitnexus Cligitnexus-cli is a Claude Code skill for the GitNexus CLI that helps developers index local Git repositories into a searchable knowledge graph and manage those indexes from the terminal. The project-local runner resolves via node .gitnexus/run.cjs or auto-selects global gitnexus, pnpm dlx, or npx without requiring a global install. Running npx gitnexus analyze indexes symbols and dependencies, writes .gitnexus/meta.json, generates AGENTS.md and CLAUDE.md context files, installs per-repo agent skills, and optionally builds embeddings when symbol count stays under 50,000. gitnexus wiki generates LLM-powered module documentation from the graph, defaulting to gpt-4o-mini. Developers reach for gitnexus-cli when asked to index a repo, reanalyze after commits, check index status, clean stale indexes, or generate a repository wiki for agent workflows.687installs6Gitnexus Guidegitnexus-guide is the canonical onboarding skill for GitNexus, the codebase knowledge-graph MCP server. The guide tells agents to start by reading gitnexus://repo/{name}/context for a repository overview and index freshness, then match tasks to specialized GitNexus skills and follow each skill's checklist. Developers and agents reach for gitnexus-guide when asking what GitNexus tools exist, how to query the graph, which MCP resources are available, or how to run impact analysis, debugging, and refactoring workflows. It centralizes tool names, graph schema notes, and workflow references so agents do not invent incorrect GitNexus usage. Outputs are accurate tool invocation paths, resource URIs, and step-by-step workflows for code understanding tasks across the GitNexus skill family.648installs7Gitnexus Pr Swarm ReviewThis skill runs a GitNexus production-readiness pull request review using a coordinated reviewer swarm. It acts as a swarm coordinator that dispatches seven reviewer personas as subagents, runs review lanes in dependency order, and gates the final review behind a synthesis critic whose required-corrections section must be empty before output. A developer invokes it on a PR URL or number to get a structured production-readiness review. It stays read-only and never edits, commits, or posts.216installs8Gitnexus Pdg QueryThis skill is expert reference knowledge for GitNexus's pdg_query MCP tool and the control- and data-dependence edges it reads. It explains the two query modes: 'controls' (control-dependence, CDG) to find which predicate guards a statement, and 'flows' (reaching-definition data dependence) to trace where a variable flows inside a function. A developer uses it when querying or extending GitNexus's program-dependence graph, discovering guard clauses, or debugging an empty or surprising pdg_query result. It documents the opt-in --pdg layers, the anchored-and-bounded query contract, and the corrected guard-clause Cypher.185installs9Gitnexus Taint AnalysisThis skill is expert reference knowledge for GitNexus's opt-in --pdg taint-analysis subsystem: control-flow graphs, reaching definitions, and intra- plus inter-procedural taint. It explains how source-to-sink data-flow findings are computed, minus sanitizers, and how per-function summaries are composed over the call graph. A developer uses it when adding a source, sink, or sanitizer, reviewing the taint code, or debugging why the explain tool did or did not report a flow. It documents the layered substrate, the pure-solver contract, and the sanitizer kind-set model.185installs