Menu
Search patterns for RepoQL - semantic search, scoping, and question reranking.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Diagnose and fix RepoQL issues. Use when a RepoQL tool call fails or errors, results seem wrong or incomplete, indexing or queries are slow, a directory isn't being indexed or isn't recognized as a workspace, an imported repo won't appear, semantic search or explain returns nothing, or the host is unresponsive.
How to write clear, verifiable, discoverable documents for LLMs and humans. Always use when writing north-star, gestalt, reference, research, design, plan, flow, findings, concepts, or process documents.
Effective Mermaid diagrams. Use when creating markdown documents with human audiences.
Core guidance for RepoQL - when to use it vs raw file reads, and the explore workflow.
Build a Claude Code status line powered by RepoQL — blend the session transcript with the indexed graph (cost, cache, tools, index state, dashboard link) and avoid the footguns that make a status line break or lie. Use when writing or extending a status-line script.
Effective use of RepoQL — the workflow, the techniques, and the wild magic. Use when you want to get more out of RepoQL or need to understand what's possible.
| name | repoql-search |
| description | Search patterns for RepoQL - semantic search, scoping, and question reranking. |
RepoQL provides multiple search approaches. Choose based on what you're looking for.
Hybrid lexical + semantic search with ranked results.
repoql_explore(
keywords="authentication flow",
tokenBudget=1500
)
Semantic + lexical hybrid search.
SELECT * FROM search('config validation', k := 10)
Find by function/type name.
SELECT * FROM search_symbol('ValidateToken')
SELECT * FROM search_symbol('Auth%') -- Wildcards
Use uriGlob parameter with glob patterns:
uriGlob="file:///src/**/*.cs" -- All C# in src
uriGlob="file:///src/services/**" -- Services folder
uriGlob="file:///tests/**" -- Tests only
Filter in WHERE clause:
SELECT * FROM search('error', k := 20)
WHERE uri LIKE 'file:///src/%'
SELECT * FROM search('validation', k := 10)
WHERE lang = 'typescript'
Use keywords to retrieve candidates and question to rerank them toward the specific answer you need.
repoql_explore(
keywords="cache invalidation",
question="When does the read cache get evicted after writes?",
tokenBudget=3000
)
For a broad survey, omit question. For a precise investigation, include it.
Use breadth when you want more or fewer results. 0 or omitted lets RepoQL choose.
repoql_explore(
keywords="handler dispatcher",
breadth=8,
tokenBudget=3000
)
repoql_explore(
keywords="error handling",
question="Where are user-facing errors normalized before returning responses?",
uriGlob="file:///src/**",
tokenBudget=2000
)
Questions work well as keywords:
Be specific when possible:
Use multiple searches:
Combine search with read for targeted content:
# Find relevant files
repoql_explore(keywords="error handling", tokenBudget=1000)
# Read specific file with budget
repoql_read(uri="file:///src/ErrorHandler.cs", tokenBudget=3000)
# Or add question for synthesis
repoql_explain(
question="What error types are handled?",
uriGlob="file:///src/ErrorHandler.cs",
tokenBudget=2000
)