log-hygiene

What problem does it solve?

Vague error messages, high-volume log noise, and missing instrumentation make debugging slow and time-consuming, requiring engineers to manually sift through irrelevant entries to find root causes.

Core Features & Use Cases

• Log Clustering & Triage: Automatically groups recent log entries by error type and frequency to prioritize the most impactful issues to fix first.
• Actionable Error Rewriting: Rewrites ambiguous error messages to follow a standardized 4-part format (what was attempted, actual values, likely cause, disambiguation) to eliminate guesswork.
• Non-Destructive Noise Reduction: Downgrades high-volume, low-signal log entries to lower severity levels without deleting them, preserving data for future debugging sessions.
• Use Case: A team running Cloudflare Workers that produces hundreds of identical "operation failed" errors per day can use this skill to rewrite those errors to include specific failed operation details and downgrade redundant health check logs to reduce alert fatigue.

Quick Start

Use the log-hygiene skill to assess the last 24 hours of logs for your Cloudflare Worker and generate a report of proposed observability improvements.