Menu
Deep investigation of GitHub issues with root cause analysis and proposed solutions. Use when asked to investigate, analyze, or dig into an issue.
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
Generate a project spec or ticket spec. Use when asked to spec, define, design, or write a ticket for a project or task.
Triage GitHub issues or Linear tickets — classify type, assess priority, check reproducibility, detect duplicates. Use when asked to triage, assess, or categorize issues.
Plan and perform manual tests for Storyblok monoblok packages against a real, seeded Storyblok space
Drive multiple GitHub issues through the full pipeline (triage, investigate, plan, implement) in parallel. Use when asked to blitz, batch-process, or work multiple issues.
Use when writing documentation. Provides a writing style guide and content structure patterns.
Execute an approved implementation plan. Use when asked to implement, build, or code a planned change.
| name | investigate |
| description | Deep investigation of GitHub issues with root cause analysis and proposed solutions. Use when asked to investigate, analyze, or dig into an issue. |
| model | opus |
| context | fork |
| agent | investigator |
| effort | high |
Investigate the following GitHub issue: $ARGUMENTS
DX-123 or linear.app URL → Linear ticket#123, bare number, or github.com URL → GitHub issuegh issue view <number> --json title,body,labels,comments,author,createdAt,statebash .agents/skills/triage/scripts/linear-fetch.sh issue DX-123pkg:* tagspackages/ — use labels and keywords to identifygit log --oneline -20 -- packages/<name>gh issue list --search "<keywords>" --state all --limit 10Determine category: bug in logic, API change, type mismatch, missing validation, race condition, environment issue, configuration, or documentation gap.
For each root cause: the fix (file paths + line numbers), test coverage needed, verification commands.
424 → 424, ticket DX-296 → DX-296, text → slugified)mkdir -p claude-outputclaude-output/investigate-<identifier>.mdclaude-output/investigate-<identifier>.md"# Investigation: Issue #<number>
**Title:** | **URL:** | **Created:** | **State:** | **Author:**
## Summary
## Affected Package(s) (table: Package, Confidence, Evidence)
## Issue Details (Reported Behavior, Expected Behavior, Environment, Reproduction Steps)
## Code Analysis (Relevant Files table, Execution Flow, Code snippets)
## Root Cause (Category, Explanation, Evidence)
## Proposed Solutions (Changes table, Code before/after, Tests to add, Verification)
## Similar Issues
## Notes / Risks
## Next Steps