logs

Enforce structured logging standards with templates and parameters across services.

Updated Apr 9, 2026

Search Tags:#security #logging #diagnostics #code-quality #pr-review #structured-logging

Ready to run

npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill logs-sergeumatyasov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: logs
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/logs
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill logs-sergeumatyasov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logs are often inconsistent, making diagnosis slower and increasing noise in production telemetry.

Core Features & Use Cases

Standardizes log message templates across modules to ensure consistent structure, context, and severity.
Guides PR reviews and code changes to adopt structured logging, include correlation IDs, and avoid logging secrets.
Use Case: When adding a feature, apply the logging standard to produce actionable, secure, and searchable logs.

Quick Start

Apply the logging standard to a new module by updating its log messages to follow the template and include context.

Frequently Asked Questions about logs

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

FAQPage Schema

How do I standardize logs across microservices for better incident diagnostics?▼

Standardize logs by enforcing unified message templates, contextual data, and consistent severity levels across services to reduce production noise and accelerate incident diagnostics during code reviews.

What is structured logging and how does it avoid string interpolation?▼

Structured logging replaces string interpolation with parameterized templates, allowing you to pass context as structured data to ensure messages remain searchable, safe, and consistent across new modules.

How do I review PRs to ensure code quality and prevent logging secrets?▼

Review PRs by checking that log messages follow structured templates, include correlation IDs, use appropriate log levels, and explicitly avoid logging secrets to ensure secure and actionable diagnostics.

When do I need to include correlation IDs in my application logs?▼

Include correlation IDs in application logs when adding new features or modules, as they provide necessary contextual links across services to produce searchable, actionable, and consistent diagnostics.

What is the best way to reduce production noise from inconsistent log levels?▼

Reduce production noise by applying a unified logging standard that governs appropriate log levels, message structure, and contextual data, ensuring only actionable diagnostics are emitted across services.