vera

Search indexed repositories semantically to locate code by behavior, symbol, or pattern.

Updated Nov 10, 2013
One-click install
npx skills add https://github.com/bnferguson/dotfiles --skill vera-bnferguson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vera
Source: https://github.com/bnferguson/dotfiles/tree/main/.agents/skills/vera
Command: npx skills add https://github.com/bnferguson/dotfiles --skill vera-bnferguson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finding where logic lives in an unfamiliar codebase is slow with grep and file skimming. Vera indexes a repository and answers questions like "where is JWT expiry handled" or "who calls parse_config" with ranked, line-cited results. ## Core Features & Use Cases - Semantic code search: vera search "OAuth token refresh" returns ranked code blocks with path:line citations, with filters for language, path, symbol type, and git-scoped diffs. - Structural and reference queries: vera structural definitions, vera structural routes, and vera references <symbol> answer definition, caller, and callee questions directly from the call graph. - Scoped exact matching: vera grep runs regex over only indexed files, respecting .veraignore rules. - Use Case: Onboarding into a new repository, run vera overview for languages and entry points, then vera search "env file loading decision" to find configuration logic without reading the README or directory tree. ## Quick Start Ask the agent to run vera overview in the current repository and then search for how a specific feature is implemented.

Frequently Asked Questions about vera

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search a codebase semantically instead of using grep?▼

Run vera index . at the repository root, then use vera search with a behavioral phrase like "JWT expiry handling" rather than a single noun. Add --lang, --path, or --type filters to narrow results, and use --compact for signature-only output.

How do I find who calls a function in a repository?▼

Use vera references <symbol> to list callers from the call graph built during indexing, or vera references <symbol> --callees to see what the function calls. For the definition itself, run vera structural definitions <symbol>.

When should I use ripgrep instead of semantic code search?▼

Use rg for file-name searches, counting occurrences, bulk find-and-replace preparation, and files outside the Vera index such as vendored dependencies. Use vera grep when you want regex results scoped to indexed files with .veraignore rules applied.

Why does vera report no index found?▼

The repository has not been indexed yet or the command ran outside any indexed directory. Run vera index . from the repository root; search commands then resolve the nearest .vera directory from any subdirectory.

How do I fix stale search results after editing code?▼

Run vera update . from any directory to refresh the repository root's index, or vera watch . to keep it updated continuously. A stale-index warning does not invalidate existing hits, but re-indexing reflects recent edits.

Can Vera search only files changed in my branch?▼

Yes, add --changed for modified, staged, and untracked files, --since <rev> for changes since a revision, or --base <rev> for changes since the merge base. These git scopes work with search, grep, structural, and overview commands.