skills.rest
ricoisme
ricoismeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dotnet-find-bugs

Diagnose bugs and security vulnerabilities in .NET/C# codebases using CLI tools.

Updated Jan 26, 2026
Search Tags:#code quality#csharp#performance#debugging#security#dotnet
One-click install
npx skills add https://github.com/ricoisme/vscode-agents --skill dotnet-find-bugs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-find-bugs
Source: https://github.com/ricoisme/vscode-agents/tree/main/skills/dotnet-find-bugs
Command: npx skills add https://github.com/ricoisme/vscode-agents --skill dotnet-find-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers find and fix bugs, security vulnerabilities, and code quality issues in their .NET/C# codebases, especially within local branch changes.

Core Features & Use Cases

  • Bug Detection: Identifies common errors, exceptions, and performance bottlenecks.
  • Security Analysis: Scans for security vulnerabilities like injection risks and insecure deserialization.
  • CLI-First Diagnosis: Utilizes .NET CLI tools for deep, command-line-driven analysis of dumps, traces, and counters.
  • Use Case: When a .NET application is experiencing high CPU usage or frequent crashes, this Skill can be used to collect diagnostic data, analyze memory dumps, and pinpoint the root cause of the performance issue or crash.

Quick Start

Use the dotnet-find-bugs skill to analyze the current branch for any bugs or security vulnerabilities.

Frequently Asked Questions about dotnet-find-bugs

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

FAQPage Schema
How do I find memory leaks and deadlocks in a .NET application?▼

To find memory leaks and deadlocks in a .NET application, you can analyze memory dumps and traces using CLI tools like `dotnet-dump` and `dotnet-trace` to pinpoint runtime issues and identify the root cause of crashes.

How do I diagnose high CPU usage in my C# code?▼

Diagnose high CPU usage in C# code by collecting diagnostic data with `dotnet-counters` and `dotnet-trace`, enabling in-depth command-line analysis of performance bottlenecks and frequent crashes within your local branch changes.

Can I scan my local branch for security vulnerabilities in C#?▼

Yes, you can scan local branch changes for security vulnerabilities in C# to identify risks like injection flaws and insecure deserialization, helping fix security issues before merging your .NET codebase.

What's the best way to analyze .NET runtime issues without an IDE?▼

The best way to analyze .NET runtime issues without an IDE is a CLI-first approach using `dotnet-dump`, `dotnet-counters`, and `dotnet-trace` to collect and analyze diagnostic data directly from the command line.

Do I need .NET CLI diagnostic tools to debug my codebase?▼

Yes, utilizing .NET CLI diagnostic tools like `dotnet-dump`, `dotnet-counters`, and `dotnet-trace` is required to collect diagnostic data and perform in-depth analysis of runtime issues, memory leaks, and deadlocks in your codebase.

Related Skills

Explore More Software Engineering Skills→
mohitmishra786mohitmishra786
159

fuzzing

Automate coverage-guided fuzzing with libFuzzer and AFL++ for C/C++ codebases.

Community
Advanced
MesteriisMesteriis

fix-security-finding

Apply targeted patches to fix a single security vulnerability.

Community
Advanced
kevintsengtwkevintsengtw
28

dotnet-testing-code-coverage-analysis

Measure and interpret .NET code coverage with Coverlet and ReportGenerator.

Community
Intermediate
managedcodemanagedcode
466

dotnet-profiling

Diagnose .NET application performance using dotnet-trace, dotnet-counters, and dotnet-gcdump.

Official
Intermediate