Vexor CLI FAQs

Question 1

When should I use this skill instead of standard search?

Accepted Answer

You should use Vexor CLI when navigating medium-to-large repositories where you don't know the exact file structure, or when searching for a concept (like 'authentication flow') rather than a specific function name. It is significantly more effective than manual browsing or standard grep for discovery tasks.

Question 2

What does the Vexor CLI skill do?

Accepted Answer

The Vexor CLI skill enables Claude to perform semantic, intent-based searches across a codebase. Instead of looking for exact text strings, it uses vector embeddings to understand the meaning of a query, helping you find where specific features or logic are implemented regardless of the exact naming conventions used.

Question 3

How does this skill improve my AI coding workflow?

Accepted Answer

It reduces the 'context window' noise by pinpointing the most relevant files immediately. Instead of Claude guessing where code might be or reading unnecessary files, Vexor CLI provides high-accuracy starting points, saving time and API tokens during complex refactoring or debugging.

Question 4

What specialized search modes are available?

Accepted Answer

Vexor CLI offers multiple indexing strategies including 'code' mode for language-aware chunking (Python, JS, TS), 'outline' mode for Markdown documentation, 'brief' for summaries, and 'name' for lightning-fast filename discovery.

Question 5

Does it respect my project's privacy and ignored files?

Accepted Answer

Yes. By default, the skill respects your .gitignore file and excludes hidden dotfiles. However, you can use granular controls like --include-hidden or --no-respect-gitignore if you specifically need to search through those areas.

Vexor CLI

Vexor CLI

About

Key Features

Use Cases

About

Key Features

Use Cases