cmd-sentry-trace

Trace and validate user actions across the Vivreal stack using Sentry logs, traces, errors, and events.

Updated May 12, 2026
One-click install
npx skills add https://github.com/HillBombCreations/vivreal-skills --skill cmd-sentry-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-sentry-trace
Source: https://github.com/HillBombCreations/vivreal-skills/tree/main/vivreal-sentry/skills/cmd-sentry-trace
Command: npx skills add https://github.com/HillBombCreations/vivreal-skills --skill cmd-sentry-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you trace and validate user actions across the Vivreal stack using Sentry logs, traces, errors, and events, allowing for cross-correlation of frontend, backend, and WebSocket telemetry.

Core Features & Use Cases

  • Action Tracing: Trace user actions like "I just created a collection object" or "what happened when I logged in".
  • Error Investigation: Investigate errors using issue IDs, Sentry URLs, or error descriptions.
  • Deployment Validation: Validate deployments like "validate deploy CMS" or "is the portal deploy working".
  • Cross-Service Correlation: Correlate trace IDs and reconstruct distributed traces.
  • Health Check: Check the health of the system with "health check" or "is everything working".
  • DevTools Network Request: Analyze network requests from browser DevTools.
  • Tenant-Scoped Triage: Triage issues for specific tenants.
  • Request ID Fallback: Correlate request IDs when trace IDs are missing.
  • Breadcrumb Deep-Dive: Inspect breadcrumbs on specific issues.

Quick Start

Use the /sentry-trace command with your query, such as "trace the /app/content request".

Frequently Asked Questions about cmd-sentry-trace

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

FAQPage Schema
How do I trace user actions across frontend and backend services using Sentry?

Trace user actions across the Vivreal stack by correlating Sentry logs, traces, errors, and events. This enables cross-service correlation of frontend, backend, and WebSocket telemetry to validate actions like creating collection objects or logging in.

Can I investigate Sentry errors using an issue ID or Sentry URL?

Investigate Sentry errors using issue IDs, Sentry URLs, or error descriptions. The tool correlates request IDs when trace IDs are missing and allows breadcrumb deep-dives to inspect specific issues thoroughly.

What is the best way to validate deployments and check system health with Sentry logs?

Validate deployments and check system health using Sentry logs and events. You can verify if a portal deploy is working or perform a general health check to ensure everything is functioning correctly across the stack.

How do I analyze DevTools network requests and correlate distributed traces?

Analyze DevTools network requests and correlate distributed traces by reconstructing them from trace IDs. When trace IDs are missing, request ID fallback correlation and tenant-scoped triage help reconstruct the user journey.

Does Sentry cross-service correlation work for tenant-scoped issue triage?

Sentry cross-service correlation supports tenant-scoped triage to isolate issues for specific tenants. It correlates frontend, backend, and WebSocket telemetry to provide a comprehensive view of tenant-specific actions and errors.