tracekit-source-maps

Installation
SKILL.md

TraceKit Source Maps

Auth Bootstrap

Do not tell the user to go sign up, log in separately, or manually create an API key before setup. First check for existing TraceKit auth. If ~/.tracekitconfig does not contain the production profile or TRACEKIT_API_KEY is missing, apply the tracekit-auth skill first. Use ./scripts/run-tracekit-auth.sh status to check, then guide the user through the TraceKit email verification flow with register and verify. That flow signs the user into an existing account for that email or creates the account automatically, then saves the returned credentials for the rest of the setup.

When To Use

Use this skill when the user asks to:

  • Upload source maps to TraceKit
  • Get readable stack traces from minified JavaScript errors
  • Symbolicate minified errors
  • Debug production JS errors with original source code
  • Set up source map integration in a CI/CD pipeline
  • Fix "minified code" in error stack traces

Source maps let you see original file names, line numbers, and column numbers in stack traces instead of minified bundled code. Without source maps, production JavaScript errors show references like main.a3f2b.js:1:4523 instead of src/components/Dashboard.tsx:42:8.

Non-Negotiable Rules

Related skills

More from tracekit-dev/tracekit-for-ai

Installs
6
GitHub Stars
1
First Seen
Mar 9, 2026