Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

read-the-trace

Étoiles2

Forks0

Mis à jour12 juillet 2026 à 12:09

Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

YaoYinYing

YaoYinYing/REvoDesign

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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

Read the Trace

LLMs love to see "TypeError" and generate a generic fix without reading the trace. Don't.

Find the deepest frame in YOUR code — not the library frame at the top. That's where the bad value entered.
Read the actual values: what was null/undefined/wrong-type, and where it came from.
Trace it one level up: why was that value bad? The root is usually 1-2 frames above the throw.
Reproduce with that exact input before fixing. A TypeError can mean a hundred things. The trace tells you which one — read all of it, including the "caused by".

Plus depuis ce dépôt

même dépôt

adversarial-verify

YaoYinYing/REvoDesign

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.

2026-07-122

authz-check

YaoYinYing/REvoDesign

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

2026-07-122

bisect-regression

YaoYinYing/REvoDesign

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

2026-07-122

changelog-from-diff

YaoYinYing/REvoDesign

Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.

2026-07-122

clean-commits

YaoYinYing/REvoDesign

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

2026-07-122

context-budget

YaoYinYing/REvoDesign

Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.

2026-07-122

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

Read the Trace

LLMs love to see "TypeError" and generate a generic fix without reading the trace. Don't.

Find the deepest frame in YOUR code — not the library frame at the top. That's where the bad value entered.
Read the actual values: what was null/undefined/wrong-type, and where it came from.
Trace it one level up: why was that value bad? The root is usually 1-2 frames above the throw.
Reproduce with that exact input before fixing. A TypeError can mean a hundred things. The trace tells you which one — read all of it, including the "caused by".