How does the skill handle different log levels?

It categorizes logs into four distinct levels: INFO for the service narrative, DEBUG for granular troubleshooting, WARN for recoverable errors, and ERROR for failures that require handling.

Can I apply logging changes to specific parts of my code?

Yes, the skill accepts scope arguments (file, module, or all) to allow you to target specific areas of your project for logging updates.

Does this skill work with existing logging frameworks?

Yes, the skill is designed to use framework-provided logging tools, such as HTTP interceptors and built-in hooks, to ensure best practices are followed.

What is the 'Signal over Noise' principle?

It is a core philosophy where every log statement must earn its place. The skill audits logs to ensure they help diagnose issues rather than cluttering output with useless information.

Smart Logging Manager

Name: Smart Logging Manager
Author: JSai23

byJSai23

•

分析と監視

Optimizes application logging by implementing structured, signal-heavy patterns across files and modules.

The logging skill acts as an intelligent log-writer agent that audits and refines your codebase's observability strategy. Following a strict 'Signal over Noise' philosophy, it helps you eliminate redundant log statements while ensuring critical service events, state transitions, and error contexts are captured at the appropriate severity levels. Whether you are cleaning up a noisy production environment or establishing a new logging architecture, this skill ensures your logs remain readable, actionable, and focused on helping you diagnose issues effectively.

主な機能

01Scope-based targeting for specific files, modules, or the entire project

02Integration with framework-provided logging hooks and HTTP interceptors

03Standardized categorization across INFO, DEBUG, WARN, and ERROR levels

04Signal over Noise auditing to eliminate redundant or useless logs

05Context-aware error logging including attempted actions and relevant IDs

061 GitHub stars

ユースケース

01Adding missing observability to external-facing events like database connections or API requests

02Standardizing logging levels across a multi-developer project for consistent debugging

03Cleaning up 'noisy' codebases where excessive logging obscures critical runtime data

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jsai23/claude-tooling logging

For use in Claude.ai and ChatGPT