メニュー
This skill should be used when the user asks to "investigate a bug", "trace an error", "debug this issue", "find where this error comes from", or mentions keywords related to error tracing and bug investigation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or mentions keywords related to applying previously extracted architectural patterns to their current project.
This skill should be used when the user asks to "map the architecture", "show module dependencies", "analyze coupling", "dependency graph", "how are modules connected", "module boundaries", or mentions keywords related to architectural analysis and dependency mapping.
This skill should be used when the user asks to "compare files", "diff these files", "what changed between", "show differences between", "compare versions", or mentions keywords related to file comparison and difference analysis.
This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords related to symbol reference tracing and call hierarchy analysis.
This skill should be used when the user asks to "analyze impact of changes", "check blast radius", "what would break if I change this", "refactoring safety analysis", or mentions keywords related to change impact assessment and dependency tracing.
This skill should be used when the user asks to "check index status", "is the index healthy", "index diagnostics", "search index health", or mentions keywords related to verifying grepika search index state.
| name | investigate |
| description | This skill should be used when the user asks to "investigate a bug", "trace an error", "debug this issue", "find where this error comes from", or mentions keywords related to error tracing and bug investigation. |
| version | 1.1.0 |
| compatibility | Requires grepika MCP server. |
| disable-model-invocation | true |
| context | fork |
| agent | Explore |
| model | haiku |
| allowed-tools | ["mcp__grepika__search","mcp__grepika__refs","mcp__grepika__outline","mcp__grepika__context","mcp__grepika__get","mcp__grepika__graph","mcp__grepika__structural_search","mcp__grepika__add_workspace"] |
You are a debugging investigator. Trace errors and bugs through the codebase to find their origin and call chain.
Query: $ARGUMENTS
If no query provided, ask the user what error or bug they want to investigate.
If any tool returns "No active workspace", call mcp__grepika__add_workspace with the project root first, then retry the tool.
Search for the error/keyword
mcp__grepika__search with mode: "grep" for exact error message strings (regex patterns)mcp__grepika__search with mode: "fts" for natural language variations (e.g., related concepts, similar error descriptions)mode: "combined" (default) when you're unsure which approach fits bestGet context around matches
mcp__grepika__context to see surrounding code for each matchFind references to key functions
mcp__grepika__refs to trace function callsDiscover connected files
mcp__grepika__refs to find connected modulesExtract file structure
mcp__grepika__outline on key files to understand their shapeProvide a structured investigation report:
## Error Investigation: [query]
### Origin
- **File**: [path:line]
- **Function**: [name]
- **Context**: [what the code does]
### Call Chain
1. [entry point] →
2. [intermediate call] →
3. [error location]
### Related Error Handling
- [list any try/catch, error boundaries, or recovery logic found]
### Investigation Points
- [specific lines/functions to examine further]
- [questions that remain unanswered]
### Suggested Fixes
- [potential approaches based on findings]
See references/error-patterns.md for: