logging-standards

Standardize Python module logging and prevent root logger misuse.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill logging-standards-strategicmilk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging-standards
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/.claude/skills/logging-standards
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill logging-standards-strategicmilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent logging configurations and unsafe practices lead to noisy output, loss of hierarchy, and potential exposure of sensitive data across Vetinari modules.

Core Features & Use Cases

  • Defines a module‑level logger initialization pattern that preserves hierarchy.
  • Specifies appropriate log levels with concrete usage examples for debugging, information, warnings, errors, exceptions, and critical failures.
  • Provides formatting guidelines, structured data logging, and rules for handling sensitive information.
  • Offers volume control recommendations and a migration path from print statements to proper logging.
  • Ideal for developers implementing new components or refactoring existing code to meet Vetinari’s logging standards.

Quick Start

Request the logging‑standards skill to create a correct logger setup for a module and demonstrate each log level usage.

Frequently Asked Questions about logging-standards

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

FAQPage Schema
How do I set up standardized logging in Python to prevent root logger misuse?

Standardized logging prevents root logger misuse by defining a module-level logger initialization pattern that preserves hierarchy. This ensures consistent output and prevents noisy logs across Vetinari Python modules.

What is the best way to migrate from print statements to structured logging in Python?

Migrating from print statements to structured logging involves replacing prints with appropriate log levels and incorporating structured data entries. This standardization provides better volume control and safer data handling for development and production environments.

When do I need structured log entries and how do I handle sensitive information?

Structured log entries are needed when standardizing logging practices for development and production. You handle sensitive information by following specific formatting guidelines that prevent exposing vulnerable data during log generation.

Does Python logging support specific usage examples for different log levels like debugging and critical failures?

Python logging supports specific usage examples for debugging, information, warnings, errors, exceptions, and critical failures. The logging standards specify appropriate log levels with concrete examples to guide proper implementation across modules.

Why does inconsistent logging configuration cause loss of hierarchy and noisy output?

Inconsistent logging configuration causes loss of hierarchy and noisy output because unsafe practices disrupt the root logger structure. Standardizing module-level initialization preserves the logging hierarchy and ensures clean, controlled output.