crash-report

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

37|2|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill crash-report-jellyrock
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crash-report
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/crash-report
Command: npx skills add https://github.com/jellyrock/jellyrock --skill crash-report-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires source-map, adm-zip.

What problem does it solve?

Roku developers receive weekly crash report CSVs but manually creating GitHub issues for each unique crash is tedious and error-prone. This Skill automates the entire pipeline from CSV ingestion to tracked issue creation, including source map resolution and noise filtering.

Core Features & Use Cases

  • Automated Issue Creation: Parses Roku crash CSVs (or ZIPs), groups crashes by signature, and creates GitHub issues for above-threshold crashes.
  • Source Map Resolution: Resolves transpiled .brs:line references back to original .bs:line source locations using generated source maps.
  • Noise Filtering: Suppresses known, accepted crashes using a configurable noise pattern list, with spike detection to alert on anomalies.
  • Dedup & Regression Tracking: Comments on existing open issues and reopens closed issues as regressions when crashes reappear.

Quick Start

Use the crash-report skill to process the attached Roku crash CSV file and automatically create GitHub issues for each unique above-threshold crash.

Frequently Asked Questions about crash-report

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

FAQPage Schema
How do I automate Roku crash report triage from CSV files into GitHub issues?▼

Roku crash report triage automation parses weekly CSV files, groups crashes by signature, and automatically creates GitHub issues for unique crashes that exceed a configurable threshold. It uses Node.js to handle CSV parsing and the GitHub CLI to create and track issues.

How does source map resolution work for transpiled BrightScript crash reports?▼

Source map resolution for transpiled BrightScript crash reports uses the Mozilla source-map library to map .brs line references back to original .bs source locations. This ensures GitHub issues contain accurate source file and line numbers for debugging.

Can I automatically suppress known Roku crashes and filter noise from weekly reports?▼

Yes, you can suppress known Roku crashes using a configurable noise pattern list to filter accepted crashes from weekly reports. The pipeline also includes spike detection to alert on anomalies when crash frequencies suddenly increase.

Do I need Node.js and GitHub CLI to process Roku crash CSVs and create tracked issues?▼

Yes, Node.js and the GitHub CLI are required to process Roku crash CSVs and create tracked issues. Node.js handles CSV parsing, ZIP extraction, and source-map resolution, while the GitHub CLI manages issue creation, commenting, and reopening regressions.

How do I track Roku crash regressions and deduplicate existing GitHub issues?▼

Roku crash regressions are tracked by deduplicating crash signatures against existing GitHub issues. The automation comments on open issues with new occurrences and automatically reopens closed issues when a previously resolved crash signature reappears.