SKILL_NAME_PLACEHOLDER

Centralize and trace full-stack errors with Sentry integration.

2|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Agentient/vibekit --skill skill-name-placeholder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SKILL_NAME_PLACEHOLDER
Source: https://github.com/Agentient/vibekit/tree/main/skills/agentient-observability/skills/full-stack-error-tracking-with-sentry
Command: npx skills add https://github.com/Agentient/vibekit --skill skill-name-placeholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and traces full-stack errors to improve observability.

Core Features & Use Cases

  • Error aggregation: Collects errors across frontend, backend, and services into a unified view.
  • Root-cause analysis: Traces errors to their source across stack traces, sessions, and breadcrumbs.
  • Use Case: When a new exception occurs in production, quickly identify impacted users and fix the issue.

Quick Start

Initialize a Sentry integration and generate a test error to verify visibility.

Frequently Asked Questions about SKILL_NAME_PLACEHOLDER

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

FAQPage Schema
How do I trace production errors across distributed services?

Trace production errors across distributed services by centralizing error aggregation into a unified view. This captures stack traces, breadcrumbs, and user context to enable deterministic root-cause investigation across frontend and backend environments.

What is the best way to perform root-cause analysis on full-stack exceptions?

Root-cause analysis for full-stack exceptions is performed by tracing errors to their source across captured sessions and breadcrumbs. Grouping related errors and reviewing user context enables quick identification of impacted users during production incidents.

Does Sentry integration support error tracking for both web and server-side applications?

Sentry integration supports error tracking for both web and server-side applications. It captures exceptions via SDKs across distributed services in production and staging, providing error grouping and full observability for your application stack.

How do I set up error tracking and generate a test error to verify visibility?

Set up error tracking by initializing a Sentry integration with your application SDKs. After configuration, generate a test error to verify visibility and ensure that stack traces, breadcrumbs, and user context are successfully captured for monitoring.

Why do I need error grouping and breadcrumbs for production monitoring?

Error grouping and breadcrumbs are needed for production monitoring to centralize full-stack errors and improve observability. Breadcrumbs provide chronological event context leading up to an exception, while grouping aggregates similar errors for faster investigation.

Can I identify impacted users when a new exception occurs in staging?

Identify impacted users when a new exception occurs in staging by utilizing captured user context and session data. The centralized tracing mechanism aggregates these errors, allowing you to quickly review affected sessions and fix the issue.