auto-logging

Enforce structured logging with typed fields and appropriate log levels.

6|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill auto-logging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-logging
Source: https://github.com/Corvalis-LLC/Crow-Stack/tree/main/skills/auto-logging
Command: npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill auto-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logging discipline: log level selection, structured fields, what to log vs what not to log, and the specific logging anti-patterns Claude defaults to. Corrects flat log levels, over-logging, string interpolation, and log-and-propagate. Use when adding logging, reviewing log output, or designing observability.

Core Features & Use Cases

  • Enforces appropriate log levels and prevents log spam.
  • Promotes structured fields over string interpolation for filterable telemetry.
  • Provides guidance for spans, events, correlation ids, and instrumentation to improve observability.
  • Use case examples include debugging, performance monitoring, and incident response.

Quick Start

Audit your current logging practices and refactor to structured fields with correlation IDs and duration metrics.

Frequently Asked Questions about auto-logging

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

FAQPage Schema
How do I replace string interpolation with structured logging in my codebase?

Structured logging replaces ad-hoc string logs with typed fields, ensuring telemetry remains filterable. You enforce constraints on log levels and structured fields to correct flat logging and prevent log spam, improving observability across services.

What are common logging anti-patterns that cause log spam and over-logging?

Common logging anti-patterns include flat log levels, over-logging, string interpolation, and log-and-propagate behaviors. Correcting these involves enforcing appropriate log level selection and using structured fields to ensure safe and maintainable logging practices.

How do I add correlation IDs and spans for tracing across multiple services?

Adding correlation IDs and spans for tracing requires applying specific constraints on span usage and instrumentation. This provides guidance for events and correlation IDs, ensuring clear observability across services and languages for performance monitoring.

What is the best way to audit current logging practices for incident response?

Auditing current logging practices for incident response involves reviewing log output and refactoring to structured fields. You apply constraints on log levels and instrumentation to ensure safe, maintainable logging that improves observability.

When should I not use structured logging for observability?

Structured logging may not suit contexts lacking clear observability requirements across services. If a project does not need filterable telemetry or typed fields, the constraints on spans, events, and instrumentation may introduce unnecessary overhead.

Does auto-logging work with multiple languages for performance monitoring?

Auto-logging applies to software engineering projects requiring clear observability across services and languages. It specifies constraints on log levels, structured fields, and instrumentation to ensure safe and maintainable logging for performance monitoring.