本文へ移動
cccskills
無料GitHub で公開

gitnexus-cli

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"

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

GitNexus CLI Commands

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.

Commands

analyze — Build or refresh the index

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.

FlagEffect
--forceForce full re-index even if up to date
--embeddingsEnable embedding generation for semantic search (off by default)
--drop-embeddingsDrop 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.

status — Check index freshness

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.

clean — Delete the index

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.

FlagEffect
--forceSkip confirmation prompt
--allClean all indexed repos, not just the current one

wiki — Generate documentation from the graph

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).

FlagEffect
--forceForce 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)
--gistPublish wiki as a public GitHub Gist

list — Show all indexed repos

direnv exec . 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

Troubleshooting

  • "Not inside a git repository": Run from a directory inside a git repo
  • Index is stale after re-analyzing: Restart Claude Code to reload the MCP server
  • Embeddings slow: Omit --embeddings (it's off by default) or set OPENAI_API_KEY for faster API-based embedding

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

adapters

無料

Skill for the Adapters area of paddock. 108 symbols across 22 files.

日本語の概要は準備中です。原文の説明を表示しています。

racecraft-lab/Paddock122026年6月26日 更新

chat

無料

Skill for the Chat area of paddock. 62 symbols across 10 files.

日本語の概要は準備中です。原文の説明を表示しています。

racecraft-lab/Paddock122026年6月26日 更新

dashboard

無料

Skill for the Dashboard area of paddock. 80 symbols across 16 files.

日本語の概要は準備中です。原文の説明を表示しています。

racecraft-lab/Paddock122026年6月26日 更新

github

無料

Skill for the Github area of paddock. 23 symbols across 5 files.

日本語の概要は準備中です。原文の説明を表示しています。

racecraft-lab/Paddock122026年6月26日 更新

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"

日本語の概要は準備中です。原文の説明を表示しています。

racecraft-lab/Paddock122026年6月26日 更新

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"

日本語の概要は準備中です。原文の説明を表示しています。

racecraft-lab/Paddock122026年6月26日 更新

racecraft-lab のスキルをすべて見る

このスキルの問題を報告する