dev-structured-logs
SolidMigrate legacy string-based logging in .NET/C# code to structured logging templates, insert CommandHandler logging scopes, and validate or update Serilog File sink settings in appsettings JSON files. Use when users ask to modernize ILogger or Serilog usage through safe rewrites, run dry-run logging migration previews, apply structured logging rewrites, or enforce JSON file sink formatter and path conventions. For general backend design and observability guidance use $software-csharp-backend, for NUnit test design use $qa-testing-nunit, and for pipeline changes use $ops-nuke-cicd.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- vasilyu1983
- Repository
- vasilyu1983/AI-Agents-public
- Created
- 10 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
logging
Use when adding logging to an application, reviewing log output, choosing log levels, structuring logs for observability, or configuring logging backends — covers structured logging, YAML config patterns, what NOT to log, and local vs. production output.
logging
Serilog structured logging for ASP.NET Core — setup, message templates, LogContext enrichment, request logging middleware, and log level guidelines.
structured-logging
Use when adding, reviewing, or cleaning up application logging — what to log and at which level, structured fields, correlation ids, cardinality and volume, redacting sensitive data, and sampling. Triggers on log statements in a diff, "add logging", noisy or useless logs, log costs, or an incident where the logs didn't answer the question.