vexor-cli

Vexor CLI Skill

When to Use

• You need to locate files by intent rather than exact filename or text match.
• The repository is large enough that manual browsing or naive grep is too slow or ambiguous.
• You want semantic discovery of where something is implemented, loaded, defined, or documented.

Goal

Find files by intent (what they do), not exact text.

Use It Like This

• Use vexor first for intent-based file discovery.
• If vexor is missing, follow references/install-vexor.md.

Command

vexor "<QUERY>" [--path <ROOT>] [--mode <MODE>] [--ext .py,.md] [--exclude-pattern <PATTERN>] [--top 5] [--format rich|porcelain|porcelain-z]

Common Flags

• --path/-p: root directory (default: current dir)
• --mode/-m: indexing/search strategy
• --ext/-e: limit file extensions (e.g., .py,.md)
• --exclude-pattern: exclude paths by gitignore-style pattern (repeatable; .js → **/*.js)
• --top/-k: number of results
• --include-hidden: include dotfiles
• --no-respect-gitignore: include ignored files
• --no-recursive: only the top directory
• --format: rich (default) or porcelain/porcelain-z for scripts
• --no-cache: in-memory only, do not read/write index cache

Modes (pick the cheapest that works)

• auto: routes by file type (default)
• name: filename-only (fastest)
• head: first lines only (fast)
• brief: keyword s