code-review-severity-icons

name	code-review-severity-icons
description	Use during every code review process to format review findings with severity icons while preserving high, medium, and low classifications.

Code Review Severity Icons

Use this skill whenever you produce code review findings or inline review comments.

Goal

Keep the existing severity classification behavior, but make each finding visually scannable by adding the matching icon to the review comment text.

Severity Format

Prefix every review finding comment with the icon and severity label:

Severity	Icon	Comment prefix
High	🛑	🛑 **High:**
Medium	⚠️	⚠️ **Medium:**
Low	🍦	🍦 **Low:**

Review Instructions

1. Classify each finding as high, medium, or low using the normal code review severity criteria.
2. Add the matching icon to the beginning of the comment body.
3. Preserve any structured severity metadata the review system already uses; the icon is an addition to the human-readable comment text, not a replacement.
4. Do not add a severity icon to non-finding text such as acknowledgements, summaries, or "no findings" responses.

Examples

🛑 **High:** This endpoint trusts the caller-provided user id, allowing users to read another user's records. Resolve the user id from the authenticated principal instead.

⚠️ **Medium:** This query loads all todo items before filtering by status. Move the filter into the database query so larger lists remain responsive.

🍦 **Low:** This helper name is ambiguous. Consider renaming it to describe the date parsing behavior.

Querying Microsoft Documentation

You have access to MCP tools called microsoft_docs_search, microsoft_docs_fetch, and microsoft_code_sample_search - these tools allow you to search through and fetch Microsoft's latest official documentation and code samples, and that information might be more detailed or newer than what's in your training data set.

When reviewing code that uses native Microsoft technologies, such as C#, F#, ASP.NET Core, Microsoft.Extensions, NuGet, Entity Framework, or the dotnet runtime, query the Microsoft Learn MCP documentation tools to validate specific or narrowly defined technical details before making related findings.

For C# and .NET reviews, use the Learn MCP tools to validate documentation about the C# types, .NET types, members, APIs, attributes, and framework behaviors used in the changed code. Do not rely only on memory when a finding depends on the documented behavior, supported usage, overloads, lifecycle, disposal requirements, threading guarantees, configuration semantics, or version-specific behavior of those types.