/crash-backtrace — DEPRECATED (use /crash-report's enrich phase)
SkillFiles & storageDEPRECATED — superseded by /crash-report's built-in `enrich` phase. The old flow filed crash issues first and enriched them one-by-one afterward; the new enrich-before-file flow (stage → enrich → file) pulls the dashboard backtrace BEFORE filing, so issues are born complete and architectural-class crashes route to their epic instead of becoming standalone issues. Do not invoke for new work — run /crash-report and paste backtraces during its enrich step. Retained only as a redirect; the `enrich-issue` script subcommand still exists as a legacy escape hatch for a pre-migration already-filed issue.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the /crash-backtrace — DEPRECATED (use /crash-report's enrich phase) skill
What this skill tells your AI
The instructions your AI receives, as published by jellyrock/jellyrock in .claude/skills/crash-backtrace/SKILL.md and read by ahel’s review.
This skill is deprecated. Backtrace enrichment now happens inside /crash-report, before filing, not as a separate follow-up after.
Why
The old two-step flow (file issues from the CSV → then enrich each one from the dashboard) filed before the exception code was known, so architectural-class noise (too-many-task-threads, server timeouts) got filed as standalone issues and had to be walked back. The reordered stage → enrich → file flow folds the pasted backtraces in during enrich, extracts each &hNN, and routes every crash to its disposition (file / aggregate / watch) before any GitHub write. Issues are born complete; architectural classes upsert onto their epic. The dashboard-backtrace parser is shared — it's the same scripts/crash-report.js code both flows used.
What to do instead
- Processing a weekly report? Run
/crash-report <path>and paste the dashboard backtraces during its Step 3 — Enrich. - Enriching a single pre-migration already-filed
[crash]issue (the only remaining niche)? The legacy script command still works directly:node scripts/crash-report.js enrich-issue --issue <N> --backtrace-file <path>
See docs/dev/crash-reports.md for the dashboard click-through and the plaintext-backtrace shape.
Signals
- GitHub stars
- 41
- Forks
- 2
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
crash-backtrace- Source
- github.com/jellyrock/jellyrock