stack-trace-js-probe

Generates npm, node, and tsc diagnostic checks for JavaScript and TypeScript stack traces.

6.8k|540|Updated May 6, 2026
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-js-probe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stack-trace-js-probe
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/bundled/stack-trace-js-probe
Command: npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-js-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When investigating JavaScript or TypeScript stack traces, engineers often miss language-specific failure modes like async boundary issues, undefined property access, JSON parsing errors, or module resolution problems. This Skill provides a structured probe that produces targeted checks, reproduction commands, and patch targets for JS/TS traces.

Core Features & Use Cases

  • Language-Specific Checks: Identifies async boundary, undefined property, JSON parsing, and module-resolution issues, plus TypeScript type-contract checks when .ts/.tsx files appear.
  • Reproduction Guidance: Suggests minimal node, npm, vitest, jest, or ts-node reproduction commands based on the trace context.
  • Patch Targets: Recommends fixes such as optional chaining, schema validation, discriminated unions, or error wrapping, along with verification commands like npm test or npx tsc --noEmit.
  • Use Case: While triaging a TypeScript service crash, invoke this probe to get a checklist of likely causes, a minimal ts-node reproducer, and a tsc --noEmit verification step.

Quick Start

Ask the agent to analyze this JavaScript stack trace and produce npm-specific checks, a reproduction command, and patch targets.

Frequently Asked Questions about stack-trace-js-probe

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

FAQPage Schema
How do I debug a JavaScript stack trace with npm-specific checks?▼

Run a structured probe that checks async boundaries, undefined property access, JSON parsing, and module resolution against the trace. It then suggests a minimal node or npm reproduction command and verification via npm test.

How to reproduce a TypeScript error from a stack trace?▼

Identify the failing file and line from the trace, then build a minimal ts-node or vitest reproduction snippet. Verify the fix with npx tsc --noEmit to confirm type contracts hold without emitting output.

What patch targets fix undefined property errors in TypeScript?▼

Common patch targets include optional chaining for nullable access, schema validation at input boundaries, discriminated unions for variant handling, and error wrapping to preserve context across async boundaries.

When should I use vitest vs jest for reproducing test failures?▼

Choose based on the test runner already present in the project context from the trace. If the context does not identify a package manager or runner, fall back to generic npm test -- <pattern> or npx tsc --noEmit examples.

Can this probe be invoked directly by users?▼

No, it is an internal helper for the meta-stack-trace-investigator skill with user-invocable set to false and model invocation disabled. It activates only as part of the parent investigation workflow.