skills.rest
iterate
iterateOFFICIAL
Explore all skills by this author →
Website𝕏@iterateGitHub

debug-os-worker

Correlate Cloudflare OS worker observability events to request-level regressions and code locations.

198|19|Updated Sep 15, 2025
Search Tags:#observability#cloudflare#orpc#request tracing#production incident#code correlation#worker debugging
One-click install
npx skills add https://github.com/iterate/iterate --skill debug-os-worker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-os-worker
Source: https://github.com/iterate/iterate/tree/main/.opencode/skills/debug-os-worker
Command: npx skills add https://github.com/iterate/iterate --skill debug-os-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging production or preview 500s in the Cloudflare OS worker is difficult because you need evidence across observability events and then map that evidence back to the exact handler code.

Core Features & Use Cases

  • Query Worker observability events: Retrieve recent events (typically 20–50) and filter by service/trigger, message, requestId, error text, and level.
  • Narrow to error-focused signals: Isolate likely root causes by filtering for error-level events or distinctive message fragments from alerts.
  • Correlate failures to code paths: Trace findings to the relevant sections of apps/os source code, especially entry.workerd.ts, apps/os/src/orpc/, and apps/os/src/domains/.

Quick Start

Use the debug-os-worker skill to query the last 30 minutes of deployed worker events for environment OS, filter to the specific error message or requestId from your alert, then identify the corresponding handler code under apps/os/src/.

Frequently Asked Questions about debug-os-worker

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

FAQPage Schema
How do I debug Cloudflare Worker 500 errors in production?▼

Debug Cloudflare Worker 500 errors by querying observability events via the Cloudflare MCP server, filtering by error text or requestId, and mapping the correlated failure evidence to specific handler code under apps/os/src/.

What is the best way to trace a specific requestId in a Cloudflare OS worker?▼

Trace a requestId by querying recent worker observability events and applying the requestId filter to isolate error-level signals, then correlating those findings to relevant code paths in apps/os/src/orpc/ and apps/os/src/domains/.

Why are my Cloudflare Worker logs missing during an alert-driven investigation?▼

Missing Cloudflare Worker logs during alert-driven investigation require narrowing observability event queries by scope, trigger, and message fragment to retrieve the correct recent events needed for code correlation.

Can I use request tracing to map oRPC handler failures in production?▼

Yes, request tracing maps oRPC handler failures by locating observability evidence from deployed worker events and mapping that correlated failure evidence to specific oRPC handler code locations under apps/os/src/.

How do I find the root cause of a production incident using Cloudflare observability events?▼

Find the root cause of a production incident by querying Cloudflare observability events, narrowing results to error-focused signals using level and message filters, and tracing findings to corresponding code in apps/os/src/.

Related Skills

Explore More Software Engineering Skills→
vallafedericovallafederico

solidstart-websocket

Adds endpoint-level WS support to SolidStart apps with lifecycle management.

Community
Intermediate
nikrichnikrich
1

configuring-tauri-csp

Configure CSP directives in tauri.conf.json for Tauri desktop apps.

Community
Intermediate
AgentiveCityAgentiveCity
2

cloudflare-observability-logging-monitoring

Configure structured logging, tracing, and Sentry integration for Cloudflare Workers.

Official
Advanced
jjmendezrodriguezjjmendezrodriguez

code-logging

Standardize TypeScript production logging with pino and PostHog.

Community
Intermediate