fix-logging

Audit and fix log calls with correct levels and context in source files.

1|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/HYP3R00T/voicepad --skill fix-logging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-logging
Source: https://github.com/HYP3R00T/voicepad/tree/main/.agents/skills/fix-logging
Command: npx skills add https://github.com/HYP3R00T/voicepad --skill fix-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and fix logging in codebases to ensure every significant event is logged with the right level and enough context, helping diagnose failures from log files without reproducing issues.

Core Features & Use Cases

  • Enforces log-level conventions (debug, info, warning, error) and prevents silent failures.
  • Audits all log calls across target files, ensuring context such as file paths, operation names, and numerical values are included.
  • Provides actionable guidance and fixes to insert missing logs or adjust log levels to improve observability across development, staging, and production.

Quick Start

Run fix-logging on the target source files to audit all log calls and insert missing context-aware logs.

Frequently Asked Questions about fix-logging

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

FAQPage Schema
How do I audit codebase logging to find missing context and miscategorized log levels?

Auditing codebase logging involves scanning target source files to detect miscategorized log levels, missing context like file paths, and silent failures. This ensures every significant event is logged with appropriate level and actionable context.

How do I fix silent failures in error-handling paths by inserting missing logs?

Fix silent failures by auditing error-handling paths to insert missing logs with appropriate warning or error levels. This provides necessary context such as operation names and numerical values to diagnose issues without reproducing them.

What is the best way to enforce log-level conventions across source files?

Enforcing log-level conventions requires auditing all log calls across target files to ensure debug, info, warning, and error levels follow standards. Placeholder-based formatting and operation names must be applied to prevent double-logging.

Does this logging audit approach work with existing codebases that lack structured logging?

This logging audit approach works with existing codebases by auditing all log calls across functions to add context-aware logs. It applies placeholder-based formatting and file paths to ensure robust observability across development, staging, and production.

How do I prevent double-logging when adding context-aware logs to functions?

Prevent double-logging by auditing all existing log calls across target source files before inserting new ones. Ensure placeholder-based formatting is applied and log levels follow conventions to avoid redundant entries during error handling.