review-logging-patterns

Transform scattered console logs into structured wide events with contextual data.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/suiramdev/terryscord-new --skill review-logging-patterns-suiramdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-logging-patterns
Source: https://github.com/suiramdev/terryscord-new/tree/main/.agents/skills/review-logging-patterns
Command: npx skills add https://github.com/suiramdev/terryscord-new --skill review-logging-patterns-suiramdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transform scattered console.log statements into structured wide events and replace generic errors with self-documenting structured errors to improve observability and debugging.

Core Features & Use Cases

  • Guides code reviews across Nuxt, Next.js, TanStack Start, Nitro, Hono, Cloudflare Workers, and standalone TypeScript to unify logging patterns.
  • Provides templates and patterns for converting console logs to wide events, enriching context, and safely structuring errors for better traceability.
  • Includes references and examples covering drain pipelines, enrichers, and structured-errors integration to accelerate adoption.

Quick Start

Analyze a sample repository to identify three logging anti-patterns and convert them into a single wide event with rich context.

Frequently Asked Questions about review-logging-patterns

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

FAQPage Schema
How do I convert console logs to structured wide events in TypeScript?

You convert console logs to structured wide events by identifying logging anti-patterns and transforming scattered statements into single wide events enriched with contextual data. This improves observability and debugging across TypeScript environments.

What are wide events and how do they improve code logging?

Wide events are structured log entries containing rich contextual data in a single payload. They improve code logging by replacing scattered console logs with self-documenting records, enabling better observability and traceability.

Does this logging pattern approach work with Nuxt, Nitro, and Cloudflare Workers?

Yes, this logging pattern approach works with Nuxt, Nitro, Cloudflare Workers, Next.js, TanStack Start, Hono, and standalone TypeScript. It unifies logging patterns across these platforms for consistent code reviews.

What's the best way to structure errors for better traceability in JavaScript applications?

The best way to structure errors is replacing generic errors with self-documenting structured errors. This pattern integrates with enrichers and drain pipelines to provide safe logging practices and rich contextual traceability.

How do I review code logging patterns to identify anti-patterns?

You review code logging patterns by analyzing a sample repository to identify anti-patterns, then applying reference-guided improvements to convert them into structured wide events with safe logging practices and enrichers.