Sentry Error Tracking
Makes the agent wire Sentry error tracking and performance spans into Node.js services
- Stars
- 10,043
- Licence
- MIT
- Files
- 1 file
What it does
Once installed, the agent follows a set of Sentry v8 patterns whenever it writes error handling, new controllers or routes, cron jobs, or database calls. It is told to send every error to Sentry rather than only logging it to the console, to wrap cron jobs and slow operations in performance spans, and to attach user, service and environment context to reports. The skill is a set of instructions and code examples; it does not itself connect to Sentry.
Great for
- Node.js/TypeScript teams already using Sentry who want consistent error capture across services
- Developers adding monitoring to cron jobs or background workers
- Teams using Prisma-style database calls who want query timing visible in Sentry
Skip it if
- Projects that do not use Sentry or Node.js: the examples assume @sentry/node and TypeScript, so the guidance will not fit other stacks without rework
- Anyone expecting it to set up a Sentry account or DSN: the skill only shows code, and you must supply your own DSN, which is a secret that should stay out of source control
- Code where sending every error to a third party is not allowed, such as systems holding sensitive personal data, since the examples attach user IDs and workflow metadata to error reports
Try asking
- “Add Sentry error handling to this new Express route for creating invoices”
- “Instrument our nightly cleanup cron job with Sentry spans and exit codes”
- “Wrap these Prisma queries in performance spans so we can see slow database calls”
- “Set up instrument.ts for our notifications service with Sentry v8 and profiling”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
error-tracking.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip error-tracking.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip error-tracking.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Give the agent your existing BaseController or error helper file so it reuses your conventions instead of the sample names.
- Keep the DSN in environment variables and review the generated code before deploying, since the skill tells the agent to attach user IDs and metadata to errors.
- Treat the 'no exceptions' rule as a style guide: check that sensitive fields are not included in error context before shipping.
What's inside
- SKILL.md
Redistributed unmodified from diet103/claude-code-infrastructure-showcase under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.