菜单
Routes local codebase search to the right tool — keyword, semantic, or symbol. Use when searching a codebase for identifiers, tracing features across files, answering conceptual questions about local code, or exploring unfamiliar projects. Do not use for external docs, GitHub repos, or package lookups.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Structural code tools via ast-grep — search by AST pattern, and outline file/module structure. Use when a search needs code structure that grep can't express (e.g. async functions containing await, calls with specific argument shapes), or when mapping a file's or directory's symbols, exports, and imports before reading it. Do not use for text search when plain grep or LSP suffices.
Fetches library documentation from author-published llms.txt, with context7 as fallback. Use when looking up docs, API references, changelogs, or breaking changes for an external library or framework. Do not use for local code or repository source exploration.
Checks latest stable versions and deprecation status of public packages via deps.dev. Use when adding or updating dependencies, verifying whether a package is deprecated, or comparing installed versions against latest. Do not use for private registries or package documentation.
Researches source code, issues, PRs, releases, and git history in external repositories on GitHub, GitLab, or Bitbucket. Use when exploring how a library implements something, searching code across public repos, reading files from a known repo, or checking issues, PRs, and release info. Do not use for local codebase search or library documentation lookups.
| name | code-search |
| description | Routes local codebase search to the right tool — keyword, semantic, or symbol. Use when searching a codebase for identifiers, tracing features across files, answering conceptual questions about local code, or exploring unfamiliar projects. Do not use for external docs, GitHub repos, or package lookups. |
Pick the tool by the shape of the question:
mcp__plugin_ora_fff__grep. Naming variants of one identifier (e.g. ['ActorAuth', 'actor_auth']) → mcp__plugin_ora_fff__multi_grep.mcp__plugin_ora_fff__find_files (frecency-ranked, git-dirty boosted).mcp__plugin_ora_morph__codebase_search. One call replaces the grep→Read→grep loop; fall back to fff + Read only when it misses.ast-grep outline (ast-grep skill).Morph returns a synthesized answer with file:line citations. The citations are real; the synthesis can misread what the code does — Read the cited locations before relaying load-bearing conclusions.
Don't shotgun-grep a feature by OR-ing guessed names (grep "FreeGift|GiftModal|BuyXGetY|percentOff") — synonyms get missed and output drowns in noise. Learn the feature's actual name from README or directory structure, grep one specific term, and follow references.