Guide structured ILogger<T> logging placement in C# services.
npx skills add https://github.com/RushuiGuan/claude --skill csharp-logging
Please help me install this Agent Skill. Skill: csharp-logging Source: https://github.com/RushuiGuan/claude/tree/main/skills/csharp-logging Command: npx skills add https://github.com/RushuiGuan/claude --skill csharp-logging
Logging is essential for diagnosing issues in C# services; without structured, thoughtful logs, incidents become hard to reproduce.
Inject ILogger<MyService> into the service constructor and place structured log statements at the key points described in the guide.
High-intent search queries and answers about installing and using this skill.
Place C# logging statements around external calls, persisted state transitions, and swallowed exceptions to maximize diagnostic value during incident investigations or feature development.
Inject ILogger<T> into your service constructor using the concrete class name, such as ILogger<MyService>, to establish a structured logging setup pattern that ensures consistent, searchable log messages.
Structured logging in C# defines specific log levels and message phrasing to create consistent, searchable logs, making incidents easier to reproduce and diagnose without losing critical diagnostic context.
Avoid logging sensitive data in dotnet by applying structured message phrasing guidelines that explicitly exclude sensitive information while writing clear messages at appropriate log levels.
Yes, this logging approach applies across typical service patterns in ASP.NET Core or .NET 10 codebases, supporting both active feature development and retrospective incident investigation workflows.
twofoldtech-dakotaImplement dependency injection and layered architecture in C#/.NET backend projects.
n4vyshAggregate and query logs with Loki using LogQL.
ironkid90Guide building, reviewing, refactoring, and architecting ASP.NET Core web applications.
willyu1007Instrument backend services with logging, error tracking, metrics, and tracing.
