skills.rest
FaysilAlshareef
FaysilAlshareefCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose root causes of . .NET build and runtime failures with structured debugging workflows.

4|1|Updated Mar 15, 2026
Search Tags:#workflow#testing#debugging#build#diagnosis#dotnet#root-cause
One-click install
npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill systematic-debugging-faysilalshareef
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/FaysilAlshareef/dotnet-ai-kit/tree/main/skills/workflow/systematic-debugging
Command: npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill systematic-debugging-faysilalshareef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined debugging workflow to prevent guesswork, reduce thrash, and ensure fixes address the true root cause of failing tests, build errors, runtime exceptions, and unexpected behavior in .NET projects.

Core Features & Use Cases

  • Structured four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation to guide developers step-by-step.
  • Evidence-first approach: reproduce failures, gather stack traces and layered data flow, and compare against working examples before changing code.
  • Safety and escalation: create failing tests before fixes, limit changes to one variable at a time, and escalate after repeated failed attempts to avoid architectural band-aids.
  • Use Case: debugging a CI build that fails after a recent merge by tracing the error to a misconfigured DI registration, writing a failing test, and applying a minimal targeted fix.

Quick Start

Use systematic-debugging to reproduce the failure, collect full error output and traces, form a single hypothesis, write a failing test that reproduces the bug, then implement the minimal fix and verify all tests pass.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of failing .NET tests instead of guessing fixes?▼

To find the root cause of failing .NET tests, reproduce the failure, collect full stack traces, compare against working examples, form a single hypothesis, and write a failing test before applying a minimal fix.

What is the best way to debug CI build errors in multi-project layered architectures?▼

The best way to debug CI build errors in multi-project layered architectures is systematically reproducing the failure locally, analyzing full error output and data flow, and creating a failing test before implementing a targeted fix.

Why should I write a failing test before applying a bug fix to a runtime exception?▼

Writing a failing test before applying a bug fix to a runtime exception ensures the fix addresses the true root cause, prevents guesswork, limits changes to one variable at a time, and verifies the exception is resolved.

How do I systematically diagnose runtime exceptions in .NET solutions?▼

Systematically diagnose runtime exceptions in .NET solutions by gathering full stack traces, analyzing layered data flow, comparing with working examples, testing single hypotheses, and escalating after repeated failed attempts to avoid architectural band-aids.

When should I escalate a debugging session instead of applying another patch?▼

You should escalate a debugging session instead of applying another patch after repeated failed hypothesis attempts, preventing architectural band-aids and ensuring the true root cause of build errors or failing tests is addressed.

Related Skills

Explore More Software Engineering Skills→
herdiansahherdiansah
23

debugger

Analyzes error messages and stack traces to identify root causes of software failures.

Community
Intermediate
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
hydershahhydershah

bug-debugging

Reproduce bugs, isolate root causes, and verify fixes with structured debugging.

Community
Advanced
GitnappGitnapp

node-inspect-debugger

Debug Node.js applications using inspector breakpoints and Chrome DevTools Protocol.

Community
Advanced