Dhpk Gitnexus Cli

---
name: dhpk-gitnexus-cli
description: 'Run GitNexus CLI commands (analyze, status, clean, wiki, list). Use when: indexing or re-indexing a repo, checking index freshness, generating a wiki, listing indexed repos. Not for: querying the graph (use dhpk-gitnexus-exploring), tool/schema reference (use dhpk-gitnexus-guide). Output: the npx gitnexus command to run + next step.'
metadata:
  dhpk-invocation-class: implicit-eligible
---

# GitNexus CLI Commands

The schema, tool names, and MCP resource catalog are owned by
`dhpk-gitnexus-guide`; this skill owns only CLI lifecycle commands and their
verification.

All commands work via `npx` — no global install required.

## Commands

### analyze — Build or refresh the index

```bash
npx gitnexus analyze
```

Run from the project root. This parses all source files, builds the knowledge graph, writes it to `.gitnexus/`, and generates CLAUDE.md / AGENTS.md context files.

| Flag           | Effect                                                           |
| -------------- | ---------------------------------------------------------------- |
| `--force`      | Force full re-index even if up to date                           |
| `--embeddings` | Enable embedding generation for semantic search (off by default) |
| `--drop-embeddings` | Drop existing embeddings on rebuild. By default, an `analyze` without `--embeddings` preserves them. |

**When to run:** First time in a project or after major code changes. If the
guide or context resource reports a stale index, follow the recovery contract
owned by `dhpk-gitnexus-guide` instead of improvising a refresh.

### status — Check index freshness

```bash
npx gitnexus status
```

Shows whether the current repo has a GitNexus index, when it was last updated, and symbol/relationship counts. Use this to check if re-indexing is needed.

### clean — Delete the index

```bash
npx gitnexus clean
```

Deletes the `.gitnexus/` directory and unregisters the repo from the global registry. Use before re-indexing if the index is corrupt or after removing GitNexus from a project.

| Flag      | Effect                                            |
| --------- | ------------------------------------------------- |
| `--force` | Skip confirmation prompt                          |
| `--all`   | Clean all indexed repos, not just the current one |

### wiki — Generate documentation from the graph

```bash
npx gitnexus wiki
```

Generates repository documentation from the knowledge graph using an LLM. Requires an API key (saved to `~/.gitnexus/config.json` on first use).

| Flag                | Effect                                    |
| ------------------- | ----------------------------------------- |
| `--force`           | Force full regeneration                   |
| `--model <model>`   | LLM model (default: minimax/minimax-m2.5) |
| `--base-url <url>`  | LLM API base URL                          |
| `--api-key <key>`   | LLM API key                               |
| `--concurrency <n>` | Parallel LLM calls (default: 3)           |
| `--gist`            | Publish wiki as a public GitHub Gist      |

### list — Show all indexed repos

```bash
npx gitnexus list
```

Lists all repositories registered in `~/.gitnexus/registry.json`. The MCP `list_repos` tool provides the same information.

## After Indexing

1. **Read `gitnexus://repo/{name}/context`** to verify the index loaded
2. Use the other GitNexus skills (`exploring`, `debugging`, `impact-analysis`, `refactoring`) for your task

## When NOT to Use

- You need to query or explore the graph, not manage the index → `dhpk-gitnexus-exploring` / `dhpk-gitnexus-impact-analysis` / `dhpk-gitnexus-debugging`
- You need the tool / resource / schema reference → `dhpk-gitnexus-guide`
- Not inside a git repository (there is no repo to index)

## Output

The exact `npx gitnexus` command for the user's goal, plus the next step (read `gitnexus://repo/{name}/context` to confirm, or move to the relevant gitnexus skill).

## Verification

- [ ] Command run from the git repo root
- [ ] `npx gitnexus status` confirms the index updated
- [ ] `gitnexus://repo/{name}/context` no longer reports staleness

## Troubleshooting

- **"Not inside a git repository"**: Run from a directory inside a git repo
- **MCP still shows old graph data**: Follow the stale-index recovery steps in
  `dhpk-gitnexus-guide` and restart the MCP client only when that contract calls
  for it.
- **Embeddings slow**: Omit `--embeddings` (it's off by default) or set `OPENAI_API_KEY` for faster API-based embedding