Analyze

Name: Analyze
Author: Roxabi

ASecurity

Index a repository into a GitNexus knowledge graph. Triggers: "index repo" | "analyze codebase" | "gitnexus analyze" | "build knowledge graph" | "create graph index".

9 stars
0 votes
0 copies
1 view
Added September 23, 2026

developmentjavascripttypescriptpythonrustgojavarubyc++bashnode

Security analysis

A92/100

mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 23, 2026

npx -y skills add Roxabi/roxabi-plugins --skill analyze --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analyze?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/roxabi-analyze-roxabi-plugins/badge)](https://www.skillsdirectory.com/skills/roxabi-analyze-roxabi-plugins)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: gitnexus-analyze
argument-hint: '[path] [--force] [--embeddings]'
description: Index a repository into a GitNexus knowledge graph. Triggers: "index repo" | "analyze codebase" | "gitnexus analyze" | "build knowledge graph" | "create graph index".
version: 0.1.0
allowed-tools: Bash, Read
---

# GitNexus Analyze

Index a repository into a knowledge graph — parses source files, builds call/dependency relationships, detects execution flows.

## Entry

```
/gitnexus-analyze [path]
/gitnexus-analyze --force        # Force full re-index
/gitnexus-analyze --embeddings   # Enable semantic search vectors
```

## Step 0 — Check Installation

```bash
which gitnexus || npm list -g gitnexus
```

¬found → ask user install first: `npm install -g gitnexus`.

## Step 1 — Resolve Path

No path arg → use current working directory.

Path arg → resolve to absolute path.

¬git repo at path → ask user path must be inside a git repository, or use `--skip-git` flag.

## Step 2 — Run Analysis

```bash
cd "$REPO_PATH" && gitnexus analyze $FLAGS
```

| Flag | Effect |
|------|--------|
| `--force` | Full re-index even if up to date |
| `--embeddings` | Enable vector embeddings (slower, better semantic search) |
| `--skip-git` | Index folder without `.git` directory |
| `--verbose` | Show skipped files and warnings |

## Step 3 — Parse Output

Read JSON output → extract:

| Field | Meaning |
|-------|---------|
| `stats.symbols` | Number of indexed symbols |
| `stats.relationships` | Number of relationships |
| `stats.processes` | Number of execution flows |
| `path` | Where `.gitnexus/` was created |

## Step 4 — Report

**Done:**
- Indexed `{N}` symbols, `{M}` relationships, `{P}` processes
- Graph stored at `.gitnexus/`
- Run `/gitnexus-query` to search, `/gitnexus-impact` before edits

## Error Handling

- "Not inside a git repository" → suggest `--skip-git` or change directory
- "No supported languages found" → list supported: TypeScript, JavaScript, Python, Go, Rust, Java, C++, Ruby, etc.
- "Out of memory" → large repo, suggest `--skip-git` or increase Node heap

$ARGUMENTS