review-logging-patterns

Review code logging practices for structured wide events and error handling.

8|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/daidr/irminsul --skill review-logging-patterns-daidr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-logging-patterns
Source: https://github.com/daidr/irminsul/tree/main/.agents/skills/review-logging-patterns
Command: npx skills add https://github.com/daidr/irminsul --skill review-logging-patterns-daidr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

Developers often struggle with unstructured, scattered logs making debugging and monitoring difficult; this Skill provides best practices for structured, comprehensive logging.

Core Features & Use Cases

  • Code Review Guidance: Offers checklists to improve logging consistency and quality.
  • Best Practices: Guides transforming scattergun console logs into structured wide events.
  • Use Case: Quickly review API handlers to ensure they use useLogger and structured errors for maintainability and clarity.

Quick Start

Review your code to replace multiple console.log statements with a single wide event using useLogger(event).

Frequently Asked Questions about review-logging-patterns

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

FAQPage Schema
What are structured wide events in code logging?

Structured wide events consolidate scattered information into a single comprehensive record. This approach replaces multiple console.log statements with one structured event, improving debugging and monitoring consistency.

How do I review logging practices in API handlers?

Review logging practices in API handlers by applying a checklist that ensures handlers implement useLogger and structured errors. This guarantees maintainability and clarity by replacing unstructured logs with consistent wide events.

What is the best way to replace console.log statements for debugging?

The best way to replace console.log statements for debugging is adopting structured wide events using useLogger(event). This method provides comprehensive logging guidance, ensuring proper error handling and security considerations are met.

Does this logging guidance address security considerations?

Yes, the logging guidance addresses security considerations within software engineering workflows. It provides best practices for reviewing code to ensure structured wide events and proper error handling do not expose vulnerabilities.

Why should I use evlog for code review?

Use evlog for code review to guide the transformation of scattergun console logs into structured wide events. It offers checklists to improve logging consistency, quality, and proper error handling across your codebase.