abhigyanpatwari/gitnexus
4 skills3.4k installs167k starsGitHub
Install
npx skills add https://github.com/abhigyanpatwari/gitnexusSkills in this repo
1Gitnexus Impact AnalysisGitNexus Impact Analysis is an agent skill for solo builders who refactor or extend a codebase without surprise breakages. It targets prompts like whether it is safe to change a function, what will break if you modify X, blast radius, and who uses this code—especially before non-trivial edits or commits. The prescribed workflow calls GitNexus impact tools upstream, loads execution processes from the repo URI, runs change detection against your working tree, then synthesizes risk for you. The checklist encodes depth-based severity so d=1 direct callers are treated as certain breakage while deeper hops are graded. It complements ordinary code review by grounding answers in indexed dependency and flow graphs rather than agent guesswork. Shelf placement is Ship review, but the same ritual helps during Build edits and Operate maintenance when legacy modules move. Treat stale-index errors as a hard stop until analyze refreshes the graph.912installs2Gitnexus ExploringGitNexus exploring is an agent skill that walks a repeatable workflow for understanding how a codebase works without spelunking every file by hand. Solo and indie builders use it when onboarding to a monorepo, answering “what calls this function?”, or mapping authentication and data layers before a refactor. The skill starts by reading gitnexus://repos and repo context, then runs semantic gitnexus_query calls, drills into symbols with gitnexus_context, and follows process resources for full traces. It assumes a GitNexus index exists and tells you to re-analyze when the index is stale. The audience is anyone shipping with Claude Code, Cursor, or Codex who needs architecture clarity fast. It complements normal grep-and-read loops by prioritizing execution flows and symbol graphs, so agents spend tokens on the right files and call chains rather than random directory walks.856installs3Gitnexus RefactoringGitNexus Refactoring is an agent skill that teaches a repeatable, graph-aware workflow for renaming symbols, extracting modules, splitting services, and moving code without silently breaking dependents. Solo builders using Claude Code, Cursor, or Codex on real repos benefit because the skill mandates impact analysis upstream of edits, execution-flow queries, and full incoming/outgoing context before anyone edits call sites. It encodes concrete GitNexus tool steps—impact, query, context, rename with dry_run, detect_changes—and checklists for rename versus extract scenarios so agents do not treat refactoring as a local rename in one file. The skill fits active Build sessions when structure outgrows a single file, and it remains valuable in Ship when you need evidence-backed refactors before review. It assumes a indexed GitNexus graph and nudges you to re-analyze when the index is stale.811installs4Gitnexus DebuggingGitNexus Debugging is an agent skill for solo builders who already use GitNexus to graph repo structure and execution flows. It activates when someone asks why something fails, where an error originates, or who calls a suspect function—typical Operate and late-Ship moments. The workflow starts with a natural-language or error-text query to surface related processes, pulls caller/callee context around a suspect symbol, optionally reads a gitnexus:// process resource for execution flow, and escalates to custom Cypher for call chains. A explicit checklist keeps the agent from jumping straight to random file reads without indexing coverage. When the index is stale, the skill directs a local re-analyze rather than hallucinating paths. It is integration-shaped (named GitNexus tools) but behaves as a debugging runbook, making it high value for indie SaaS and API maintainers who live in multi-service repos and need traceability without a full APM stack for every investigation.805installs