Skill · Setup and diagnostics
/investigate$investigate@planr-investigate
Diagnose a bug, regression, error, or unexplained behavior and optionally implement a bounded fix. Use for root-cause investigation, including before any fix, not planned feature delivery.
/investigatein Claude Code. Plugin command: /planr:investigate. With individual skills, select planr-investigate in the skill picker.
$investigatein Codex. These examples use CLI-managed direct skills. With the plugin, use $planr:investigate; with individual source skills, use $planr-investigate.
@planr-investigatein Cursor. These examples use CLI-managed Cursor rules. With individual source skills, select planr-investigate in the skill picker.
When to use it
Use it to
- Investigate a bug, regression, error, or unexplained behavior
- Reproduce a defect, establish its root cause, or apply a bounded fix
- Investigate why this fails
Not for
- Plan a new feature
- Run a broad product review
Prompts and commands
Diagnose a failure without changing code
Get the root cause and the evidence for it, with no edits until you decide on a fix.
Find the root cause before you fix it
Reproduce the defect, establish why it happens, then apply a bounded fix.
Track down a flaky test
Find out why a test fails some of the time before anyone changes the test.