adapters
FreeSkill for the Adapters area of paddock. 108 symbols across 22 files.
The English summary is being prepared. Showing the original description.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
In this repo, run GitNexus through direnv exec . gitnexus ... from the repo
root. The checked-in AGENTS guidance depends on the repo-local .envrc plus
ignored .envrc.local embedding settings; do not use npx here.
direnv exec . gitnexus analyze --embeddings --skip-agents-md
Run from the project root after the LM Studio embedding server is running. In a
linked worktree, copy the ignored root .envrc.local into the worktree and run
direnv allow first. This parses source files, builds the knowledge graph,
writes ignored output to .gitnexus/, and leaves the checked-in AGENTS map as
the repository source of truth.
| 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, after major code changes, or when gitnexus://repo/{name}/context reports the index is stale. In Claude Code, a PostToolUse hook detects staleness after git commit and git merge and notifies the agent to run analyze — the hook does not run analyze itself, to avoid blocking the agent for up to 120s and risking KuzuDB corruption on timeout.
direnv exec . 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.
direnv exec . 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 |
direnv exec . 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 |
direnv exec . gitnexus list
Lists all repositories registered in ~/.gitnexus/registry.json. The MCP list_repos tool provides the same information.
gitnexus://repo/{name}/context to verify the index loadedexploring, debugging, impact-analysis, refactoring) for your task--embeddings (it's off by default) or set OPENAI_API_KEY for faster API-based embeddingNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Skill for the Adapters area of paddock. 108 symbols across 22 files.
The English summary is being prepared. Showing the original description.
Skill for the Chat area of paddock. 62 symbols across 10 files.
The English summary is being prepared. Showing the original description.
Skill for the Dashboard area of paddock. 80 symbols across 16 files.
The English summary is being prepared. Showing the original description.
Skill for the Github area of paddock. 23 symbols across 5 files.
The English summary is being prepared. Showing the original description.
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"
The English summary is being prepared. Showing the original description.
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?", "What calls this function?", "Show me the auth flow"
The English summary is being prepared. Showing the original description.