Results for “error-logging”

Execution discipline with agency, instinct detection, critical safety rules, trust layer, and error resilience. v2.7 adds timeout handling, checkpointing, and decision logging.

debug-logging

Provides patterns for robust error handling across TypeScript, Python, and Go, including typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

跨 TypeScript、Python、Go 的健壮错误处理模式——涵盖类型化错误、错误边界、重试策略及优雅降级

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

Standards for structured logging and observability in Golang. Use when adding structured logging or tracing to Go services.

Python logging with the standard library logging module and structlog. Covers log levels, handlers, formatters, structured logging, and production best practices for FastAPI/Django applications. USE WHEN: user mentions "python logging", "fastapi logging", "django logging", asks about "how to log in python", "python logging module", "logging configuration python" DO NOT USE FOR: Node.js logging - use `nodejs-logging` instead, Java logging - use `slf4j` or `logback`, structlog-specific - use `structlog` skill for deep dive

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Reads and analyzes application logs for debugging and monitoring.

Provides patterns for robust error handling across TypeScript, Python, and Go, covering typed errors, error boundaries, retries, circuit breakers, and user-facing messages.

Provides a structured triage process for debugging test failures, build errors, runtime bugs, and production incidents, including steps to reproduce, localize, fix, and guard against recurrence.

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

**Server Logs:**

Provides a structured debugging workflow for diagnosing errors, test failures, and unexpected behavior, including root cause analysis and verification steps.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

Diagnose your own behavior by reading the structured logs you leave behind — turns.jsonl, events.jsonl, chat_history.jsonl, scheduler.yaml. Use when something has gone wrong (a message didn't land, a scheduled job isn't firing, a communication pattern feels off), when you need to understand a pattern over many turns, or when cost / token usage needs auditing. Covers jq query recipes and points at the debugging-jobs / debugging-communication / debugging-drift companion guides for specific failure modes.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs.

Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging, and more.

Diagnose failures from runtime evidence before editing code.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Error Handling Patterns

Design error prevention, detection, and recovery experiences that minimize user frustration.

Debugging is the scientific method under time pressure.

Structured workflow to reproduce, diagnose, plan, fix, verify, and record a bug fix, requiring a deterministic reproduction before diagnosis and minimal changes only.

Implement modern PHP error and exception handling patterns. Use when implementing exception hierarchies, error handlers, or custom exceptions in PHP.

Trigger: structured logging, tracing, telemetry, SLI metrics, SLO alerts, log formats. Scope: Performance metrics, error tracing, production telemetry. Boundary: Excludes client behavioral product funnels.

Guides Apex exception handling design: catching expected failures, bulk DML semantics, boundary-specific error translation, and logging once at the right layer.