capture

Capture exceptions and messages in Node/JavaScript apps with Sentry.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill capture-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/sentry/capture
Command: npx skills add https://github.com/theslashdojo/dojo --skill capture-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires _sentry/node, and includes scripts (resource) components.

What problem does it solve?

This Skill enables manual error reporting to Sentry and enriches events with user identity, tags, and scoped data to improve debugging and incident response.

Core Features & Use Cases

  • Manual error reporting: capture exceptions and messages with optional inline enrichment (tags, extra, level, user).
  • Breadcrumbs and context: attach contextual data to events and identify users for better incident understanding.
  • Scoped captures: use withScope to attach data for a single event without affecting global state.

Quick Start

Initialize Sentry with a valid DSN and run a simple capture-errors script to see an event appear in your dashboard.

Frequently Asked Questions about capture

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

FAQPage Schema
How do I manually capture exceptions and send them to Sentry in a Node application?

To capture exceptions in Sentry, initialize the SDK with a valid DSN and use captureException within try/catch blocks to manually report errors for incident response.

What's the best way to attach user context and breadcrumbs to Sentry error reports?

To enrich Sentry error reporting, use setUser for identity and addBreadcrumb to attach contextual data, improving debugging by providing a trail of events leading up to exceptions.

Can I add scoped data to a single Sentry error without affecting global state?

Yes, you can use withScope to attach tags, extra, or user context to a single Sentry captureException or captureMessage event without modifying the global Sentry configuration.

Does Sentry manual error reporting work for asynchronous code paths in JavaScript?

Sentry manual error reporting supports asynchronous JavaScript code paths, allowing you to capture exceptions and messages during async fetches and per-request scoped operations.

When should I use captureMessage instead of captureException for Sentry events?

Use captureMessage to manually report semantic messages with custom levels in Sentry, while captureException is specifically for reporting caught error objects and application exceptions.