Request: Source Generated Logging Skill #1009

Activity

1. github-actions

   assigned

   AbhitejJohn

   and

   webreidi

   on Aug 13, 2026
2. github-actions

   added

   enhancement

   on Aug 13, 2026
3. github-actions commented on Aug 13, 2026

   

   github-actionsBot

   on Aug 13, 2026 – with GitHub Actions

   Contributor

   More actions

   🎯 Issue Triage

   Summary: Requests a new skill that instructs the AI to always use source-generated logging (LoggerMessage/[LoggerMessage] attribute) instead of interpolated/string-based logging calls. Falls under general C#/.NET coding practices.

   Type: enhancement

   Assigned owners: @webreidi @AbhitejJohn (default repository owners per CODEOWNERS * rule — no existing skill/plugin path maps specifically to logging patterns)

   Confidence: Medium

   Similar issues: No existing open issues found for source-generated logging or similar logging-pattern skill requests; does not appear to be a duplicate.

   Triage details

   • Area mapping rationale: No dedicated logging plugin/skill exists in CODEOWNERS; assigned area-dotnet as this is a general C#/.NET best-practice topic rather than diagnostics, ASP.NET Core, or another specialized area.
   • CODEOWNERS path match: No specific path matched; fell back to default * owners (@webreidi @AbhitejJohn).
   • Confidence rationale: Medium — the request is clear and actionable, but area could arguably also touch area-dotnet-diag (logging/observability); chose area-dotnet since the ask is about coding style/best practice rather than performance diagnostics.
   • Suggested next steps: Maintainers may want to scope this as a new skill under plugins/dotnet/skills/ covering LoggerMessage source generators, ILogger high-performance logging, and avoiding string interpolation in log calls.

   Generated by Issue Triage for #1009 · auto · 23.6 AIC · ⌖ 2.96 AIC · ⊞ 9.5K · ◷
4. github-actions

   added

   Triaged

   on Aug 13, 2026