indexion-doc

Generate dependency graphs and README documentation from source code. Use when the user asks for a dependency diagram, wants to generate docs from code, or needs a project overview.

trkbt10/indexion-skills2 installsApache-2.0Synced Aug 26

Works with

Claude CodeCursorCodex CLIGitHub CopilotGemini CLI
---
name: indexion-doc
description: Generate dependency graphs and README documentation from source code. Use when the user asks for a dependency diagram, wants to generate docs from code, or needs a project overview.
license: Apache-2.0
---

# indexion doc

Generate dependency graphs and README documentation from source code analysis.

## When to Use

- User asks for a dependency graph or diagram
- User wants to generate README from doc comments
- User asks "how are these packages connected?"
- User wants to visualize project structure

## Subcommands

### `indexion doc graph` — Dependency Graph

Generate dependency diagrams in various formats.

```bash
# Mermaid format (default)
indexion doc graph <path>

# Graphviz DOT format
indexion doc graph --format=dot <path>

# D2 diagram format
indexion doc graph --format=d2 <path>

# Plain text
indexion doc graph --format=text <path>

# JSON
indexion doc graph --format=json <path>

# Custom title and output
indexion doc graph --title="My Dependencies" --output=deps.mmd <path>
```

**Options:**

| Option | Default | Description |
|--------|---------|-------------|
| `--format=FORMAT` | mermaid | Output format: mermaid, json, dot, d2, text |
| `--title=TEXT` | Module Dependencies | Diagram title |
| `--output=FILE` | stdout | Output file path |
| `--specs-dir=DIR` | kgfs | KGF specs directory |

### `indexion doc readme` — README Generation

Generate README.md from source doc comments.

```bash
# Basic README generation
indexion doc readme <path>

# Using a template
indexion doc readme --template=.indexion/state/templates/readme.md <path>

# Using doc.json configuration
indexion doc readme --config=doc.json <path>

# Per-package README generation (skips packages with existing README.md)
indexion doc readme --per-package <path>

# Filter files
indexion doc readme --include='*.mbt' --exclude='*_test.mbt' <path>

# Output to file
indexion doc readme -o=README.md <path>
```

**Options:**

| Option | Default | Description |
|--------|---------|-------------|
| `--format=FORMAT` | md | Output format: markdown, json, raw |
| `--template=FILE` | — | Template file for generation |
| `--config=FILE` | — | doc.json configuration file |
| `--per-package` | false | Generate README.md per package (skips existing READMEs) |
| `--[no-]recursive` | true | Recurse into subdirectories |
| `--include=PATTERN` | — | Include pattern (repeatable) |
| `--exclude=PATTERN` | — | Exclude pattern (repeatable) |
| `--specs-dir=DIR` | kgfs | KGF specs directory |
| `-o, --output=FILE` | stdout | Output file path |

### `indexion doc init` — Initialize Templates

Set up documentation templates.

```bash
# Initialize README template
indexion doc init <path>

# Force overwrite existing
indexion doc init --force <path>
```

## Workflow

1. Run `indexion doc init .` to set up templates
2. Run `indexion doc graph .` to understand dependencies
3. Run `indexion doc readme --template=... .` to generate/update READMEs
4. Run `indexion doc readme --per-package src/ cmd/indexion/` to generate per-package READMEs

## Dogfooding Lessons

- `doc readme --per-package` skips existing READMEs — hand-written ones are preserved
- `doc graph` output can be embedded directly in README via Mermaid code blocks
- Run `indexion grep --undocumented src/` to quickly check what still needs doc comments
  before running `doc readme`

More Writing & Documentation skills

paper-context-resolver

lllllllama/rigorpilot-skills

Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.

450.8k

repo-intake-and-plan

lllllllama/rigorpilot-skills

Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.

450.0k

minimal-run-and-audit

lllllllama/rigorpilot-skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

449.9k

← All Writing & Documentation skills

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY