| name | vexor-cli |
| description | Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | software-development |
| category | devtools |
| risk | unknown |
| source | community |
| tags | ["skill","software-development","devtools","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 summary (good for PRDs)code: code-aware chunking for .py/.js/.ts (best default for codebases)outline: Markdown headings/sections (best for docs)full: chunk full file contents (slowest, highest recall)
Troubleshooting
