From poisk
Hybrid semantic + keyword search over source code and documents via poisk. Only use when explicitly requested.
How this skill is triggered — by the user, by Claude, or both
Slash command
/poisk:searchThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search indexed source code and documents using `poisk run` — hybrid semantic + keyword search over indexed content.
Search indexed source code and documents using poisk run — hybrid semantic + keyword search over indexed content.
poisk run <query> [--top-k N] [--folders dir1,dir2]
Output format per result:
[score] file_path:line_num [symbol] (context chain)
Full chunk text...
Warnings go to stderr. Use 2>/dev/null to suppress logs.
lex:term: keyword-only (exact match via FTS5)vec:term: semantic-only (vector similarity)lex:exact | vec:similar: compose sub-queries with |lang:go, kind:markdown, sym:functionNamelex: queries for exact terms (error messages, config keys, function names)--top-k to control result count (default 20)--folders to narrow results to a specific directory# Semantic search
poisk run "how does authentication work" --top-k 10 2>/dev/null
# Exact keyword match
poisk run "lex:handleRequest" 2>/dev/null
# Combined: semantic + keyword
poisk run "vec:error handling patterns | lex:error handling" 2>/dev/null
# Filter to specific folder
poisk run "database migrations" --folders ~/projects/myapp 2>/dev/null
# Filter by language
poisk run "lang:go interface implementation" 2>/dev/null
npx claudepluginhub alexander-akhmetov/poisk --plugin poiskGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.