Menu
Trace execution paths from an error or bug report to find the root cause, gathering surrounding context (callers, imports, tests) along the way.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Gather relevant source files for a task, resolve their dependencies, and package everything into a structured context prompt.
Produce an architectural design and implementation plan based on task requirements, identifying scope, dependencies, impact, and a step-by-step rollout strategy.
Explore the codebase and export a structured context file (e.g., context.xml) for pasting into an external LLM like ChatGPT or Claude Web.
Analyze dependencies, callers, and coupling before refactoring, then produce a safe incremental refactoring plan.
Review recent code changes by gathering git diffs, identifying affected callers and tests, and analyzing for security, performance, and breaking changes.
Identify untested functions by comparing source symbols with test symbols, then prepare context for writing missing tests.
| name | rp_investigate |
| description | Trace execution paths from an error or bug report to find the root cause, gathering surrounding context (callers, imports, tests) along the way. |
Starting from a bug description or error trace, follow the execution path through the codebase to identify the root cause. Produce a Root Cause Analysis (RCA) before proposing any fix.
A Root Cause Analysis containing:
get_symbols — understand structure of files mentioned in error traceblast_radius — trace backwards from error point (find dependents)get_imports_graph — understand dependency chainget_related_tests — check if failing code has testsmanage_selection — accumulate suspect files during investigationbuild_prompt — package investigation context (use profile="bugfix")manage_selection to accumulate files as you trace — don't try to identify all files upfront.