godgrep
godgrep
Routes codebase search tasks to the right tool based on intent.
Tool Routing
| Intent | Primary tool | Also consider |
|---|---|---|
| Keyword / symbol search (exact identifier known) | mcp__plugin_ora_fff__grep |
LSP for definitions |
| Multi-pattern OR — naming variants of one identifier | mcp__plugin_ora_fff__multi_grep |
sequential mcp__plugin_ora_fff__grep calls |
| File discovery (by name) | mcp__plugin_ora_fff__find_files |
mcp__plugin_ora_fff__grep for content matches |
| Concept / "how does X work" (no identifier yet) | skim README + find_files for structure, then fff__grep + Read |
follow references from the first hit |
| Trace a flow | mcp__plugin_ora_fff__grep for a specific term, then follow refs |
mcp__plugin_ora_fff__find_files for entry points |
| Find all usages of X | LSP find-references | mcp__plugin_ora_fff__grep |
| Find a specific symbol | LSP go-to-definition | mcp__plugin_ora_fff__grep |
| Structural code patterns | ast-grep |
mcp__plugin_ora_fff__grep as fallback |
| Outside git index / fallback | shell grep / find |
last resort, after fff |
| Git history / blame | Bash (git log/blame) | — |
More from trancong12102/agentskills
deps-dev
Look up the latest stable version of any open-source package across npm, PyPI, Go, Cargo, Maven, and NuGet. Use when the user asks 'what's the latest version of X', 'what version should I use', 'is X deprecated', 'how outdated is my package.json/requirements.txt/Cargo.toml', or needs version numbers for adding or updating dependencies. Also covers pinning versions, checking if packages are maintained, or comparing installed vs latest versions. Do NOT use for private/internal packages or for looking up documentation (use context7).
151council-review
Multi-perspective code review that synthesizes findings from multiple reviewers into a unified report. Use when the user asks to review code changes, audit a diff, check code quality, review a PR, review commits, or review uncommitted changes. Also covers 'code review', 'review my changes', 'check this before I merge', or wanting multiple perspectives on code. Do not use for documentation/markdown review or trivial single-line changes.
101oracle
Deep analysis and expert reasoning. Use when the user asks for 'oracle', 'second opinion', architecture analysis, elusive bug debugging, impact assessment, security reasoning, refactoring strategy, or trade-off evaluation — problems that benefit from deep, independent reasoning. Do not use for simple factual questions, code generation, code review (use council-review), or tasks needing file modifications.
99context7
Fetch up-to-date documentation for any open-source library or framework. Use when the user asks to look up docs, check an API, find code examples, or verify how a feature works — especially with a specific library name, version migration, or phrases like 'what's the current way to...' or 'the API might have changed'. Also covers setup and configuration docs. Do NOT use for general programming concepts, internal project code, or version lookups (use deps-dev).
86conventional-commit
Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages.
58react-web-advanced
Web-specific React patterns for type-safe file-based routing, route-level data loading, server-side rendering, search param validation, code splitting, and list virtualization. Use when building React web apps with route loaders, SSR streaming, validated search params, lazy route splitting, or virtualizing large DOM lists. Do not use for React Native apps — use react-native-advanced instead.
45