From gm
Enforces mandatory iterative codebase search workflow via exec:codesearch. Starts with two-word queries, refines by changing/adding words until code elements like functions or configs are found.
npx claudepluginhub anentrypoint/gm-cc --plugin gmThis skill uses the workspace's default tool permissions.
`exec:codesearch` is the only way to search the codebase. Glob, Grep, Find, Explore are hook-blocked.
Searches codebases semantically with natural language queries to find implementations by concept (e.g., 'where is X', 'how does Y work'). Returns file paths, lines, and snippets.
Enables semantic code search by behavior, intent, or natural language to find implementations without exact names. Uses CocoIndex MCP server for unfamiliar codebases.
Enhances codebase searches via semantic query parsing, regex patterns, AST analysis, symbol lookups, and optimized grep/ripgrep with relevance ranking and context.
Share bugs, ideas, or general feedback.
exec:codesearch is the only way to search the codebase. Glob, Grep, Find, Explore are hook-blocked.
exec:codesearch
<natural language query>
Start with exactly two words. Never start broader. Never start with one word.
Iterate by changing or adding words — do not switch approach or give up until the content is found:
Never: start with one word | start with a sentence | give up after one miss | switch to a different tool | declare content missing after fewer than 4 search attempts
Each search is one exec:codesearch call. Run them sequentially — use each result to inform the next query.
Finding where a function is defined:
exec:codesearch
session cleanup idle
→ no results →
exec:codesearch
cleanup sessions timeout
→ found.
Finding config format:
exec:codesearch
plugin registration format
→ no results →
exec:codesearch
plugin config array
→ found.