crash-backtrace

What problem does it solve?

Roku's analytics dashboard only exposes crash backtraces one at a time with no bulk export option, making it extremely tedious to manually attach detailed backtrace and local variable data to already-filed crash issues in GitHub.

Core Features & Use Cases

• Auto-Issue Resolution: Automatically matches backtraces to the correct filed [crash] GitHub issue using the innermost frame signature, eliminating manual issue lookup.
• Flexible Input Handling: Accepts backtraces via file reference, inline paste, or dashboard TSV export, with support for batch processing multiple backtraces in a single invocation.
• Noise Classification: Flags known non-actionable crash patterns including one-off timeouts and init race conditions to let you skip unnecessary enrichment work.
• Use Case: After running /crash-report to file 15 crash issues from Roku's daily error report, use this skill to batch enrich all of them with their corresponding backtraces in minutes instead of clicking through the dashboard 15 separate times.

Quick Start

Use the crash-backtrace skill to enrich the crash issue matching the backtrace in the attached file 'daily-error-bt-582.txt' with its full local variable snapshot.