log-review

Audit codebases for logging and observability deficiencies.

1|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill log-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-review
Source: https://github.com/trevorbyrum/claude-skills-suite/tree/main/skills/log-review
Command: npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill log-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies critical gaps in logging and observability within a codebase, which can lead to significant debugging challenges and silent failures in production environments.

Core Features & Use Cases

  • Detects Silent Failures: Flags code that swallows errors or fails without any indication.
  • Assesses Error Context: Ensures errors are logged with sufficient detail for effective debugging.
  • Checks API Boundaries: Verifies logging at system entry and exit points.
  • Verifies Correlation & Tracing: Ensures request IDs are propagated for end-to-end traceability.
  • Improves Log Hygiene: Identifies issues like PII in logs or inconsistent formatting.
  • Use Case: Before deploying new code, run this skill to ensure that any potential issues will be logged with enough context to be quickly diagnosed and resolved in production.

Quick Start

Run a full audit of logging and observability gaps in the current project.

Frequently Asked Questions about log-review

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

FAQPage Schema
How do I find silent failures and missing error context in my codebase?

To check API boundary logging, audit logging and observability gaps to verify logging at system entry and exit points. This identifies missing API boundary logging to ensure all external requests are tracked for production readiness.

Why do I need correlation IDs for tracing and how are they verified?

To ensure production readiness, audit logging and observability gaps before deploying new code. This checks for silent failures, inadequate correlation IDs, and logging framework consistency to guarantee potential issues are quickly diagnosed in production.

What logging issues affect production debugging besides missing errors?

To audit observability gaps, run a full audit of logging and observability deficiencies in the current project. This assesses the project's observability stack, logging framework consistency, and adherence to best practices for production debugging.

Can I use this to check tracing and correlation IDs before deployment?

Yes, you can verify tracing and correlation IDs before deployment by auditing observability gaps. This ensures request IDs are propagated for end-to-end traceability, confirming your system adheres to production debugging best practices.