gitnexus-plan — Claude Code skill: graph-based change plans
gitnexus-plan turns a task description into an implementation-ready plan built from GitNexus graph navigation and live source checks, ready to hand off to an execution agent.
no license 248 installs ★ 48,719 updated 2026-10-25
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-plan -a claude-codeWhat gitnexus-plan does
gitnexus-plan has one job: produce a plan document for an engineering change that another agent, such as gitnexus-work, can act on without redoing the research. It uses the GitNexus code graph to find where to look, a statement-level data-flow graph to work out what gates and feeds the behavior, and direct reads of the current source as the final check on what's actually true. The skill itself never edits code, tests, or config.
Tasks fall into categories — local bug fix, feature, shared-API refactor, performance, security, dependency migration, concurrency, docs, architecture spike — and each one sets its own analysis depth and tool-call budget. The plan file is written only through a built-in helper, landing at docs/plans/YYYY-MM-DD-gitnexus-plan-<slug>.md; writing the destination file directly is blocked. A separate Deepen mode strengthens an existing plan, reading it back through the same helper and binding the plan's digest to its original path rather than a raw file path.
Before any graph query or file read, the skill checks a context ledger to avoid repeating a question it already answered, and it isn't allowed to invent symbol names, test names, or tool results — anything unverified goes into an assumptions section instead.
What it helps with
- plan a shared-API refactor with impact analysis before touching code
- draft a feature plan without re-exploring the whole codebase
- strengthen an existing plan through Deepen mode
- flag security and concurrency risks ahead of implementation
- hand an execution agent a plan with assumptions already called out
Example prompts for the agent
- /gitnexus-plan Add retry support to the ingestion pipeline
- /gitnexus-plan deepen docs/plans/2026-10-29-retry-pipeline.md
- Plan this change using the knowledge graph
How to install gitnexus-plan
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-plan -a claude-code2Manually: put the files in place
~/.claude/skills/gitnexus-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gitnexus-plan/
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-plan -a codex2Manually: put the files in place
.agents/skills/gitnexus-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-plan -a cursor2Manually: put the files in place
.cursor/skills/gitnexus-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install abhigyanpatwari/GitNexus gitnexus-claude-plugin/skills/gitnexus-plan2Manually: put the files in place
.github/skills/gitnexus-plan/SKILL.md1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/abhigyanpatwari/GitNexus --path gitnexus-claude-plugin/skills/gitnexus-planManually: put the files in place
.devin/skills/gitnexus-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-plan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gitnexus-plan
How do I install gitnexus-plan in Claude Code?
Run npx skills add abhigyanpatwari/GitNexus --skill gitnexus-plan -a claude-code; the skill lands at ~/.claude/skills/gitnexus-plan/SKILL.md.
What does gitnexus-plan do?
It builds an implementation-ready plan for a code change by combining GitNexus graph navigation, statement-level data-flow analysis, and direct source verification, so a follow-up agent can start work without repeating the investigation.
Can gitnexus-plan modify source code?
No, it only plans: the single repo file it writes is the plan document itself, and the only other state change allowed is refreshing the .gitnexus index via analyze --index-only.