gitnexus-cli

Execute GitNexus CLI commands to index, analyze, and document codebases.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/guideops/agentic-shared --skill gitnexus-cli-guideops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-cli
Source: https://github.com/guideops/agentic-shared/tree/main/skills/gitnexus-cli
Command: npx skills add https://github.com/guideops/agentic-shared --skill gitnexus-cli-guideops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the execution of GitNexus CLI commands, making it easier to manage indexing, analyzing, and documenting codebases.

Core Features & Use Cases

  • Indexing and Analysis: Run analyze to build or refresh the index and generate context files.
  • Status Checking: Use status to check if the current repository has a GitNexus index and when it was last updated.
  • Index Cleaning: Clean the index with clean to remove corrupted data or prepare for re-indexing.
  • Documentation Generation: Generate repository documentation with wiki.
  • Repository Listing: List all indexed repositories with list.

Quick Start

Use the gitnexus-cli skill to index and analyze your codebase by running 'gitnexus-cli analyze'.

Frequently Asked Questions about gitnexus-cli

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

FAQPage Schema
How do I index and analyze a codebase using command-line flags?

To index and analyze a codebase, run the analyze command to build or refresh the GitNexus index and generate context files. Supports various command-line flags for configuration.

How do I check if my repository has an existing code index?

To check if your repository has a code index, use the status command. It verifies if a GitNexus index exists for the current repository and reports when it was last updated.

Can I generate documentation for my repository directly from the code index?

Yes, you can generate repository documentation directly from the code index by using the wiki command. This requires an active GitNexus index to process the codebase.

What is the best way to remove corrupted index data before re-indexing a repository?

The best way to remove corrupted index data before re-indexing is to use the clean command. It clears the GitNexus index, preparing the repository for a fresh indexing run.

How do I list all repositories that have been indexed?

To list all indexed repositories, execute the list command. It queries the GitNexus system and returns a complete list of all repositories that currently have a generated index.