- Tool
- REA
- Provider or project
- JoasASantos community collection
- Source type
- Community-authored
Who should use it
Release engineers and maintainers who control both builds and have a reproducible failure.
Practical uses
- Triage a crash that appears after a packaging change.
- Turn a crash report into a concise handoff with testable hypotheses.
How to use it
- Record each build identifier and collect a sanitized stack trace from the same test input.
- Compare the top failing frames and the configuration or dependency versions for those modules.
- Request one likely cause and a minimal experiment to confirm it.
Original example
Our sample viewer opens the same local fixture in build A but crashes in build B. Compare the provided stack traces and dependency lists. Identify one changed code path to verify in a unit test.
Limitations
An optimized or stripped build may omit symbols. Correlation across builds is evidence for a hypothesis, which still needs a reproducer.
Sources and versions
The explanation and example were written for this directory. The cited files record the source version.
- Skills/reap-15-version-comparison-and-crash-work/SKILL.md
REA Investigation Prompts · JoasASantos ·
9756618f25·Source license MIT
Related prompts
Plan a WebAssembly port of your game
Identify the portable simulation code in an authorized game and plan a small browser proof of concept before migrating rendering, audio or platform integrations.
Reverse Engineering Prompts · REA
Start a read-only application investigation
Scope the first investigation of an unfamiliar application to a small question and produce an evidence map before changing code or behavior.
Reverse Engineering Prompts · REA
Trace one feature in an application you own
Follow a single visible action from the user interface to its output. Keep observations, source evidence and hypotheses distinct so the next maintainer can verify the trace.
Reverse Engineering Prompts · REA