skills.rest
jellyrock
jellyrockOFFICIAL
Explore all skills by this author →
WebsiteGitHub

crash-backtrace

Enrich GitHub crash issues with Roku backtraces and local variable snapshots.

37|2|Updated Jun 28, 2025
Search Tags:#batch-processing#source-mapping#noise-classification#error-debugging#crash-backtrace#roku-development#github-issue-enrichment
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill crash-backtrace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crash-backtrace
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/crash-backtrace
Command: npx skills add https://github.com/jellyrock/jellyrock --skill crash-backtrace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, gh, and includes scripts (resource) components.

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.

Frequently Asked Questions about crash-backtrace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch enrich GitHub crash issues with Roku backtrace data?▼

Batch enrich GitHub crash issues with Roku backtrace data by providing backtraces via file reference, inline paste, or dashboard TSV export, and the skill resolves matches and posts structured comments automatically.

Can I match Roku backtraces to existing GitHub issues automatically?▼

Yes, you can match Roku backtraces to existing GitHub issues automatically. The skill uses the innermost frame signature to resolve each backtrace to its correct filed crash issue without manual lookup.

How do I skip known noise patterns when enriching Roku crash backtraces?▼

To skip known noise patterns when enriching Roku crash backtraces, the skill classifies non-actionable crashes like one-off timeouts and init race conditions, letting you bypass unnecessary enrichment work.

Do I need GitHub CLI and Node to run crash-backtrace?▼

Yes, you need GitHub CLI and Node to run crash-backtrace, as it relies on them to resolve issue matches, apply source-mapped worktrees, and post structured enrichment comments to GitHub.

What's the best way to attach local variable snapshots to Roku crash issues?▼

The best way to attach local variable snapshots to Roku crash issues is using this skill to process batched backtraces and post the full multi-frame snapshots as structured comments on matched issues.

Related Skills

Explore More Software Engineering Skills→
jellyrockjellyrock
37

crash-report

Convert Roku crash-report CSVs into tracked GitHub issues with source-map resolution.

Official
Advanced
sipherxyzsipherxyz
1

crash-report

Parse Unreal Engine crash logs and create structured GitHub issues.

Official
Advanced
Open-CuriosityOpen-Curiosity
1.7k

gini-bug-report

Submit consent-based Gini crash reports to GitHub issues.

Official
Advanced
auerbachbauerbachb
3

prompt

Analyze GitHub issues to assess complexity and tier them for Claude Code sprint planning prompts.

Community
Advanced