Skip to content
Skills Library
Programming · Analysis

stack-trace-analysis-symbolication-source-maps

/stack-trace-analysis-symbolication-source-maps

Use this skill when decipher obfuscated stack traces using debug symbols, crash reports, and source maps.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill when decipher obfuscated stack traces using debug symbols, crash reports, and source maps.

Original author description

Use this skill when decipher obfuscated stack traces using debug symbols, crash reports, and source maps.

How it works

  1. When to use
  2. Core principles
  3. Step-by-step workflow
  4. Specifics & examples
  5. Common mistakes & pitfalls
  6. Verification checklist
  7. Related skills
Original SKILL.md headings · 41 lines, 368 words
SKILL.md preview
---
name: stack-trace-analysis-symbolication-source-maps
description: Use this skill when decipher obfuscated stack traces using debug symbols, crash reports, and source maps.
---
# Stack Trace Analysis Symbolication Source Maps

## When to use
Use this skill when decipher obfuscated stack traces using debug symbols, crash reports, and source maps. This applies across software engineering lifecycles, team code reviews, production debugging, prompt design, and architectural documentation.

## Core principles
- **Clarity Over Cleverness**: Code, prompts, and technical documentation must prioritize clarity, predictability, and long-term maintainability over obscure shortcuts.
- **Evidence-Based Engineering**: Every decision, bug resolution, and architectural choice must be supported by empirical data, minimal reproductions, or benchmark traces.
- **Cognitive Load Minimization**: Design interfaces, APIs, and documents to minimize mental parsing overhead for future engineers and autonomous agents.
- **Continuous Feedback Loops**: Incorporate automated verification, peer reviews, and post-task retrospectives to drive iterative improvement.

## Step-by-step workflow
1. **Define the objective and constraints**: State the exact technical outcome, acceptance criteria, and operational boundaries.
2. **Gather baseline telemetry and context**: Inspect relevant codebases, stack traces, system architecture diagrams, or log files.
3. **Execute structured analysis or implementation**: Apply domain-specific techniques (e.g., minimal reproduction, refactoring transforms, prompt templates).
4. **Validate against automated test assertions**: Run unit tests, linters, or schema validation parsers to verify behavioral correctness.
5. **Document rationale and trade-offs**: Record the 'why' behind choices, documenting rejected alternatives and operational considerations.
6. **Conduct retrospective review**: Share findings with stakeholders or record lessons learned in the team knowledge base.

## Specifics & examples
- **Standard Engineering Artifact**:
  - Scope: Stack Trace Analysis Symbolication Source Maps
  - Core Deliverable: Actionable, verifiable engineering guidance aligned with Debugging & troubleshooting.
  - Verification Rule: Tested against production workflows and peer-reviewed standards.
- **Primary Focus Area**: Debugging & troubleshooting principles designed to elevate engineering precision and team psychological safety.

## Common mistakes & pitfalls
- Jumping directly into speculative fixes or complex rewrites before isolating the root cause.
- Introducing premature abstractions that increase indirection and cognitive complexity.
- Failing to document context and architectural trade-offs for subsequent maintainers.

## Verification checklist
[ ] The technical deliverable or fix is validated with reproducible test assertions.
[ ] Changes preserve backwards compatibility and maintain existing contract invariants.
[ ] Documentation or commit logs clearly explain the rationale and trade-offs.

## Related skills
- git-bisect-automated-bug-hunting
- root-cause-analysis-5-whys-fishbone-diagram
- incident-postmortem-blameless-rca-authoring

Versions

The database has no other skills named stack-trace-analysis-symbolication-source-maps.

Database snapshot: 13.11.2026 · package version a76bedd99046 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91crash-debugging
    Crash log analysis, symbolication, and debugging workflows for iOS apps. Use when investigating app crashes, analyzing crash reports, symbolicating stack traces, or identifying root causes. Covers crash log retrieval, symbolication with dSYM files, stack trace analysis, and common crash patterns.
  • 100symbolication-setup
    Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
  • 100sentry-fix-stack-traces
    Make Sentry stack traces readable — upload source maps for JavaScript/TypeScript, or debug files for native and mobile (dSYM, ProGuard/R8, NDK symbols, Dart obfuscation maps, .NET PDBs). Use when frames in Sentry show minified names, bundled paths, hex addresses, "unknown", or…
  • 100stack-trace-analysis
    Reads stack traces and crash reports across Java/Kotlin, Python, JavaScript/Node, Go, .NET, Rust, and Swift/Objective-C - finds the first relevant frame, follows chained causes, recognises common failure signatures, and symbolicates native and minified traces. Use when given an…
  • 100diagnosing-stacktrace-symbolication
    Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM). The PostHog symbol-set lookup flow is universal across platforms; build-tool and…
  • 100mobiai-analyze-crash
    Use when the user shares a crash from any source (stack trace, log, screenshot, error description) and wants to find the root cause and fix it.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.