Loading...
Loading...
Found 92 Skills
Search Tool Hierarchy
Semantic code search using Phase 1 vector embeddings and Phase 2 hybrid search.
KGF-aware token pattern and semantic code search. Use when the user wants to search code by structure (not just text), find specific patterns like nested loops or undocumented functions, or search by natural language similarity.
Configure ignore patterns in GrepAI. Use this skill when excluding files and directories from indexing.
Automatically detect and suggest appropriate MCP tools (context7, grep_app, web_search) based on user queries. This applies when queries contain documentation keywords (including English terms like how to use, docs, API, guide, tutorial and Chinese terms like 如何使用, 文档, 教程); code search keywords (including English terms like example, implementation, source code, github and Chinese terms like 例子, 示例, 实现, 源码); or latest information/bug fixing keywords (including English terms like latest, 2025, 2026, new, update, fix bug, error and Chinese terms like 最新, 更新, 修复 bug, 报错).
Integrate GrepAI with Claude Code via MCP. Use this skill to enable semantic code search in Claude Code.
Install and configure Ollama for local embeddings with GrepAI. Use this skill when setting up private, local embedding generation.
AST-based code search and refactoring via ast-grep MCP
Setup and workflow for using sqry semantic code search as an MCP server with Claude Code. Covers installation, MCP configuration, tool naming conventions, and recommended search patterns. Install this skill to give Claude Code full access to sqry's 34 AST-based code analysis tools.
Search code and text files using semantic similarity and keyword matching. Use when: finding relevant code snippets, searching documentation, or locating files by content. NOT for: binary file search or regex pattern matching.
Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
Use GitHits CLI for canonical open-source examples, indexed source, docs, grep, file listing, and code navigation. Activate when verifying library behavior from source or examples. For metadata, vulnerabilities, dependency graphs, or changelogs, use githits-package instead.