gitnexus-cli

Execute GitNexus CLI commands to analyze, index, and manage repositories.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill gitnexus-cli-nullmastermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-cli
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/gitnexus/gitnexus-cli
Command: npx skills add https://github.com/nullmastermind/viber-router --skill gitnexus-cli-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitNexus CLI Commands enable users to run GitNexus CLI actions such as analyze, index, check status, clean the index, generate a wiki, and list indexed repos directly from the command line, streamlining repository knowledge management.

Core Features & Use Cases

  • CLI-driven repo management: run analyze, status, clean, wiki, and list to manage multiple repos from a single interface.
  • Automated indexing and analysis: refresh indices and generate documentation to keep CLAUDE.md / AGENTS.md context files up to date.
  • Use Case: Quickly index a project to generate a wiki and ensure the knowledge graph stays current across CI workflows.
  • Example: Index this repo, Reanalyze the codebase, Generate a wiki.
  • Note: Commands are invoked via npx — no global install required.

Quick Start

Run npx gitnexus analyze from your project root to build or refresh the index and generate context files.

Frequently Asked Questions about gitnexus-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a wiki for my git repository from the command line?

You can generate a wiki by running the GitNexus CLI wiki command via npx from your project root. This builds or refreshes your repository index and automatically generates the wiki documentation to keep your knowledge graph current.

What is the best way to automate repository analysis across multiple repos?

Automating repository analysis is handled by running the GitNexus CLI analyze command. This inspects and indexes multiple repositories from a single interface, ensuring context files like CLAUDE.md stay up to date across CI workflows.

Do I need to globally install GitNexus to inspect and manage my repositories?

No global install is required to inspect and manage repositories with GitNexus. All commands for status checks, indexing, and analysis are invoked directly via npx, streamlining repository knowledge management without local setup.

Can I use CLI commands to clean and check the status of indexed repositories?

Yes, you can use CLI commands to clean and check the status of indexed repositories. GitNexus supports the clean and status commands via npx, allowing you to easily manage and inspect your repository index.

How does repository indexing keep CLAUDE.md and AGENTS.md context files updated?

Repository indexing keeps CLAUDE.md and AGENTS.md context files updated through the GitNexus analyze command. This automated indexing process refreshes the repository knowledge graph and regenerates documentation to reflect current codebase changes.

Why should I run a repository analysis before generating a wiki?

Running a repository analysis before generating a wiki ensures your index is current. The GitNexus analyze command builds or refreshes the index first, so the subsequent wiki generation accurately reflects the latest codebase state.