gitnexus-setup
Use when directly requested to install GitNexus.
Best use case
gitnexus-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when directly requested to install GitNexus.
Teams using gitnexus-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gitnexus-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gitnexus-setup Compares
| Feature / Agent | gitnexus-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when directly requested to install GitNexus.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
<gitnexus_setup>
<role>
Installation gate for GitNexus — runs two commands, verifies the MCP connection, and hands off to GitNexus's own auto-provisioned skills and documentation.
</role>
<when_to_use_skill>
Use ONLY during workspace initialization (Phase 6 of init-workspace-flow) or when the user explicitly asks to install GitNexus.
</when_to_use_skill>
<installation>
**Prerequisites:** Node.js 18+, npm.
**Step 1 — Index the repository:**
```bash
npx gitnexus@latest analyze --skip-agents-md
```
Indexes the codebase into `.gitnexus/` and auto-provisions editor-specific skills, hooks, and context files where supported.
Add `.gitnexus` to `.gitignore` — the index is local and not committed.
**Step 2 — Register the MCP server (one-time):**
```bash
npx gitnexus@latest setup
```
Auto-detects installed editors and writes the global MCP config.
**Step 3 — Verify:**
```
/mcp
```
GitNexus should appear as `gitnexus · ✔ connected`.
</installation>
<troubleshooting>
- **MCP not connecting:** Run `npx gitnexus@latest setup` again. For project-scoped config, add `.mcp.json` to the repo root with `{"mcpServers":{"gitnexus":{"type":"stdio","command":"gitnexus","args":["mcp"]}}}`.
- **`vector`/`fts` extension errors:** These download from a third-party CDN at index time and may fail on restricted networks. Core graph navigation still works without them.
- **Slow indexing:** ~5 min for a medium repo (~4k symbols). For very large repos, use `--worker-timeout 60` to increase worker idle timeout.
- **Stale index after edits:** `gitnexus analyze` installs a PostToolUse hook that auto-refreshes. If missing, run `npx gitnexus@latest analyze` manually between sessions.
</troubleshooting>
</gitnexus_setup>Related Skills
gitnexus-cli
GitNexus CLI reference for npx commands — analyze, status, clean, wiki, list — with flags, effects, and when to run each.
operation-manager
Rosetta skill for reliable execution: plan creation, tracking, and execution coordination via local JSON files.
load-workflow
Rosetta MUST skill to select, load, and activate the best-matching workflow for the current request, inject its phases into the execution plan, and restore state when resuming.
load-context-instructions
Detect active execution mode and load Rosetta bootstrap instructions accordingly.
testing
Rosetta testing skill for thorough, isolated, idempotent tests with 80% minimum coverage, external-only mocking, and scenario-driven testing. Use when writing or updating tests.
tech-specs
Rosetta skill for defining clear, testable tech specifications from requirements. Use when creating implementation-ready documentation that defines the target state architecture, contracts, and interfaces.
subagent-contract
Rosetta MUST skill. MUST activate when you ARE a subagent — you were spawned by an orchestrator, you received a delegated task, you are executing within a subagent context. Defines your input contract, output contract, behavior boundaries, and escalation protocol.
specflow-use
Connect Rosetta locally with Grid Dynamics SpecFlow MCP. Trigger only when the user mentions SpecFlow or SpecFlow workspaces and if SpecFlow MCP is already installed.
sensitive-data
Rosetta CRITICAL MUST skill. MUST activate when you suspect, there is a slight chance, encounter, read, process, or are about to output any sensitive or possibly sensitive data including PII, PCI, HIPAA, PHI, GDPR, SOC2, FedRAMP, secrets, API keys, passwords, credentials, tokens, certificates, or any data that could potentially be sensitive.
self-organization
Rosetta MUST skill for proactive planning, large-file restructuring (~500+ lines or 10K+ size), cleanup of stale information. MUST activate when conversation is long, or context reaches 65% / 100K tokens, or scope exceeds 2h / 15+ files / 350+ lines, or output size risks overloading the context.
self-learning
Rosetta MUST skill. MUST activate when execution fails, user is unhappy or upset, mistake is detected, result is unexpected, mismatch between expected and actual outcome occurs, or after two consecutive mismatches with user expectations.
risk-assessment
Rosetta MUST skill. MUST activate before execution when environment has access to databases, cloud services, S3, or similar external systems. MUST activate when assessing environment risk level. SHOULD be invoked manually before any new environment interaction.