skills.rest
tylerbutler
tylerbutlerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

decode-stacktrace

Parse JavaScript, TypeScript, and Node.js stack traces to identify culprit commits and PRs.

Updated Jan 7, 2026
Search Tags:#git#code analysis#debugging#javascript#stack trace#error resolution#nodejs
One-click install
npx skills add https://github.com/tylerbutler/repo-overlays --skill decode-stacktrace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decode-stacktrace
Source: https://github.com/tylerbutler/repo-overlays/tree/main/tylerbutler/FluidFramework/jikim-superskills/.claude/skills/decode-stacktrace
Command: npx skills add https://github.com/tylerbutler/repo-overlays --skill decode-stacktrace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers quickly pinpoint the root cause of errors by analyzing stack traces and correlating them with code history.

Core Features & Use Cases

  • Automated Stack Trace Parsing: Extracts key information like function names, file paths, and line numbers from various JavaScript, TypeScript, and Node.js stack traces.
  • Source Code Contextualization: Maps minified or build output paths back to original source files for accurate analysis.
  • Git History Analysis: Leverages git blame and git log to identify recent changes, suspect commits, and associated pull requests.
  • Culprit Identification: Scores commits and PRs based on recency, proximity to the error, and scope to determine the most likely cause of the bug.
  • Rollback Recommendations: Suggests specific Git commands for reverting problematic changes.
  • Use Case: When a production Node.js server crashes with a cryptic stack trace, this Skill can analyze it, identify the faulty commit and PR, and suggest how to revert the change.

Quick Start

Analyze the provided stack trace to find the most likely cause and suggest a fix.

Frequently Asked Questions about decode-stacktrace

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

FAQPage Schema
How do I find the commit that caused a JavaScript stack trace error?▼

To find the commit that caused a JavaScript stack trace error, you can parse the stack frames to locate source files and analyze Git history using blame and log to identify the suspect commit. The process scores commits by recency, proximity to the error, and scope to pinpoint the most likely cause.

Can I debug minified Node.js stack traces back to the original source code?▼

Yes, you can debug minified Node.js stack traces by mapping build output paths back to original source files. This contextualization allows accurate parsing of function names, file paths, and line numbers from minified JavaScript and TypeScript server traces.

What is the best way to identify a faulty pull request from a production crash stack trace?▼

The best way to identify a faulty pull request from a production crash stack trace is by analyzing the stack frames to locate the responsible code, then leveraging Git history analysis to find associated PRs. Culprit identification scores commits based on recency, proximity, change type, and size.

How do I revert a problematic code change identified in a Node.js stack trace?▼

To revert a problematic code change identified in a Node.js stack trace, you analyze the trace to find the suspect commit, then use suggested specific Git commands for rolling back the change. This directly addresses the faulty commit and associated pull request causing the error.

Does stack trace analysis work with both TypeScript and Node.js server errors?▼

Yes, stack trace analysis works with TypeScript and Node.js server errors. Automated parsing extracts key information like function names and line numbers from various JavaScript, TypeScript, and Node.js stack traces to identify the responsible code and recent changes.

Related Skills

Explore More Software Engineering Skills→
luyi985luyi985

source-maps-debugging

Configures source maps to map compiled JavaScript back to TypeScript for debugging.

Community
Intermediate
yaresimeonthomasyaresimeonthomas

resolving-rollback-conflicts

Resolve git revert merge conflicts in CI/CD rollback workflows.

Community
Advanced
ryan-ressmeyerryan-ressmeyer

git-commits

Enforce single-line Git commit messages without Co-Authored-By trailers.

Community
Basic
beomeodevbeomeodev

ms-essentials-debug

Diagnose and fix My-Spec runtime errors with stack trace analysis and root-cause investigation.

Community
Advanced