Menu
Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.
Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.
Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.
| name | read-the-trace |
| description | Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception. |
| when_to_use | a stack trace, an exception, "TypeError/NullPointer/undefined", a crash log |
LLMs love to see "TypeError" and generate a generic fix without reading the trace. Don't.
